GHSA-g9v2-wqcj-j99g is a high-severity (CVSS 7.8) vulnerability in uptime-kuma. 1 public exploit reference exists, so weaponization risk is real. A fix is available for uptime-kuma — see the affected versions and patch details below.
Uptime Kuma has Persistentent User Sessions
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-g9v2-wqcj-j99g.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-g9v2-wqcj-j99g plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
uptime-kumanpmDescription
Summary
Attackers with access to a users' device can gain persistent account access. This is caused by missing verification of Session Tokens after password changes and/or elapsed inactivity-periods.
Details
uptime-kuma sets JWT tokens for users after successful authentication.
These tokens have the following design flaws:
- After successful login, a JWT token and it is stored in
sessionStorageorlocalStorage. Which of the two is decided based on theRemember Mebutton. The users' token is valid without any time limitation, even after long periods of inactivity. This increases the risk of session hijacking if, for example, a user forgets to log off and leaves the PC. - 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
- If a user changes a password
- any previously logged in clients are not logged out
- previously issued tokens remained valid forever
These flaws allow user cookies to remain valid even after changing passwords or being inactive, posing a high security risk.
POC
Password resets not deactivating cookies
- Log in.
- Note the user cookie.
- Change your password.
- Attempt to log in again with the same cookie.
- The cookie remains valid despite the password change.
Inactivity not deactivating sessions
In testing, even after a period of over a day of inactivity, the session was still valid
Impact
Another person with local access to the device could take over the session permanently, even after hours of previous inactivity or a password change. Such activity would not be obvious to the user (see https://github.com/louislam/uptime-kuma/issues/3481 if you want to help with this).
With this gained account access, an attacker can cause:
confidentially loss
- monitors (including private ones not shared on public status pages)
- notification providers
- settings like
api-keys(only used for accessing/metrics) - settings like secrets like the
Steam API Key - maintenance periods
availability loss
- by creating a lot of monitors and setting the retention policy very high leading to degraded database performance or out of storage
- by creating a lot of
HTTP(s) - Browser Engine (Chrome/Chromium) (Beta)leading to RAM exhaustion
integrity loss
- by the attacker deleting a monitor
- by the attacker deleting a monitor's history
- by the atacker changing the meaning of a monitor (changing where it points)
scope creep
If 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.
We 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 aware of that.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | uptime-kuma | all versions | 1.23.3npm install uptime-kuma@1.23.3 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uptime-kuma, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update uptime-kuma to 1.23.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g9v2-wqcj-j99g is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g9v2-wqcj-j99g can be triaged on real exposure rather than presence alone.
Tailored to GHSA-g9v2-wqcj-j99g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-g9v2-wqcj-j99g in your dependencies?
O3 Security finds GHSA-g9v2-wqcj-j99g across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.