Enabling Authentication does not close all logged in socket connections immediately

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary This is basically GHSA-88j4-pcx8-q4q but instead of changing passwords, when enabling authentication. PoC - Open Uptime Kuma with authentication disabled - Enable authentication using another window - Access the platform using the previously logged-in window - Note that access (read-write) remains despite the enabled authentication - Expected behaviour: - After enabling authentication, all previously connected sessions should be invalidated, requiring users to log in. - Actual behaviour: - The system retains sessions and never logs out users unless explicitly done by clicking logout or refreshing the page. Impact See GHSA-g9v2-wqcj-j99g and GHSA-88j4-pcx8-q4q TBH this is quite a niche edge case, so I don't know if this even warrants a security report.

Published by the source

19 Apr 2024, 17:26 UTC

Last modified by the source

19 Apr 2024, 17:26 UTC

Source last checked

26 Oct 2026, 12:30 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-23q2-5gf8-gjpp

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-23q2-5gf8-gjpp

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

# Patch Next advisory brief: GHSA-23q2-5gf8-gjpp

Advisory: Enabling Authentication does not close all logged in socket connections immediately
IDs: GHSA-23q2-5gf8-gjpp
Record: https://patchnext.com/advisories/ghsa-23q2-5gf8-gjpp (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
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.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm uptime-kuma: affected <= 1.23.11; fixed in 1.23.12

## 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-23q2-5gf8-gjpp (OSV record GHSA-23q2-5gf8-gjpp lists affected ranges: npm uptime-kuma >=0 <1.23.12 (fixed))
- Verified: https://github.com/advisories/GHSA-23q2-5gf8-gjpp (GitHub-reviewed advisory GHSA-23q2-5gf8-gjpp lists affected ranges: npm uptime-kuma >=0 <=1.23.11)

Commands are suggestions: review each one before running it.