How severe is GHSA-g9v2-wqcj-j99g?

GHSA-g9v2-wqcj-j99g has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-g9v2-wqcj-j99g?

GHSA-g9v2-wqcj-j99g affects the following packages: uptime-kuma (npm). Ecosystems affected: npm.

How do I fix GHSA-g9v2-wqcj-j99g?

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.

How do I detect GHSA-g9v2-wqcj-j99g in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uptime-kuma. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-g9v2-wqcj-j99g if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-g9v2-wqcj-j99g?

O3 pinpoints whether GHSA-g9v2-wqcj-j99g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-g9v2-wqcj-j99g actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-g9v2-wqcj-j99g, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-g9v2-wqcj-j99g?

GHSA-g9v2-wqcj-j99g has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g9v2-wqcj-j99g?

GHSA-g9v2-wqcj-j99g is classified as CWE-384 (CWE-384). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g9v2-wqcj-j99g published, and has it been updated?

GHSA-g9v2-wqcj-j99g was published on October 10, 2023 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-g9v2-wqcj-j99g

HIGH

Uptime Kuma has Persistentent User Sessions

Also known asCVE-2023-44400

Published

Oct 10, 2023

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk18th percentile+0.22%

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.

Blast Radius

1 pkg affected

📦uptime-kuma

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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 sessionStorage or localStorage. Which of the two is decided based on the Remember Me button. 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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`uptime-kuma`	all versions	1.23.3

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Uptime Kuma is a self-hosted monitoring tool. Prior to version 1.23.3, a…

github.comNVDOct 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uptime-kuma. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether GHSA-g9v2-wqcj-j99g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

# 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 `sessionStorage` or `localStorage`. Which of the two is decided based on the `Remember Me` button. The users' token is valid without any time limitation, even after long periods of inactivity. This

O3 Security · Impact-Aware SCA

Is GHSA-g9v2-wqcj-j99g in your dependencies?

O3 detects GHSA-g9v2-wqcj-j99g across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works