Uptime Kuma has Persistentent User Sessions

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.8 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2023-44400: 0.28% estimated exploitation activity in the next 30 days; percentile 20.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

10 Oct 2023, 21:29 UTC

Last modified by the source

4 Feb 2026, 03:43 UTC

Source last checked

26 Oct 2026, 12:27 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-g9v2-wqcj-j99g

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-g9v2-wqcj-j99g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-44400

Advisory: Uptime Kuma has Persistentent User Sessions
IDs: CVE-2023-44400, GHSA-g9v2-wqcj-j99g
Record: https://patchnext.com/advisories/cve-2023-44400 (revision 2, source checked 26 Oct 2026, 12:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: uptime-kuma 1.23.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm uptime-kuma: affected < 1.23.3; fixed in 1.23.3

## Suggested inspection (read-only)
- `npm ls uptime-kuma --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on uptime-kuma.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g9v2-wqcj-j99g (OSV record GHSA-g9v2-wqcj-j99g lists affected ranges: npm uptime-kuma >=0 <1.23.3 (fixed))
- Verified: https://github.com/advisories/GHSA-g9v2-wqcj-j99g (GitHub-reviewed advisory GHSA-g9v2-wqcj-j99g lists affected ranges: npm uptime-kuma >=0 <1.23.3)

Commands are suggestions: review each one before running it.