Skip to content

← Actionable
Medium, CVSS 6.9amended

OneUptime: Password Reset Token Logged at INFO Level

CVE-2026-32598GHSA-4524-cj9j-g4fj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (oneuptime 10.0.23), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm oneuptime

    Affected
    < 10.0.23
    Fixed in
    10.0.23

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-32598: 0.24% estimated exploitation activity in the next 30 days; percentile 15.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The password reset flow logs the complete password reset URL — containing the plaintext reset token — at INFO log level, which is enabled by default in production. Anyone with access to application logs (log aggregation, Docker logs, Kubernetes pod logs) can intercept reset tokens and perform account takeover on any user. Details Vulnerable code — App/FeatureSet/Identity/API/Authentication.ts lines 370-371: The tokenVerifyUrl is a complete URL like https://app.oneuptime.com/accounts/reset-password/<plaintext-token. This is logged at INFO level, which is enabled by default in production and persisted to stdout, log files, and any configured log aggregation systems. Additionally — login credentials logged at DEBUG level (line 909): The entire login request body (including cleartext password) is logged at DEBUG level. While DEBUG is typically disabled in production, it is commonly enabled during incident troubleshooting. No existing CVEs cover sensitive data exposure in logging…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-4524-cj9j-g4fj

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-4524-cj9j-g4fj

Agent brief

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

# Patch Next advisory brief: CVE-2026-32598

Advisory: OneUptime: Password Reset Token Logged at INFO Level
IDs: CVE-2026-32598, GHSA-4524-cj9j-g4fj
Record: https://patchnext.com/advisories/cve-2026-32598 (revision 3, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: oneuptime 10.0.23. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm oneuptime: affected < 10.0.23; fixed in 10.0.23

## Suggested inspection (read-only)
- `npm ls oneuptime --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 oneuptime.
- 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-4524-cj9j-g4fj (OSV record GHSA-4524-cj9j-g4fj lists affected ranges: npm oneuptime >=0 <10.0.23 (fixed))
- Verified: https://github.com/advisories/GHSA-4524-cj9j-g4fj (GitHub-reviewed advisory GHSA-4524-cj9j-g4fj lists affected ranges: npm oneuptime >=0 <10.0.23)

Commands are suggestions: review each one before running it.

Loading voting…