# CVE-2026-32598: OneUptime: Password Reset Token Logged at INFO Level

> Attackers with log access can steal password reset tokens from INFO logs to take over user accounts in OneUptime.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2026
- **Updated:** 14 Mar 2026
- **Also known as:** GHSA-4524-cj9j-g4fj

## What is CVE-2026-32598?

CVE-2026-32598 is a medium-severity vulnerability in oneuptime, published on 12 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OneUptime is a solution for monitoring and managing online services. Prior to 10.0.24, 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. This vulnerability is fixed in 10.0.24.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-32598?

2 open source packages ship an affected version, including oneuptime. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oneuptime` | npm | All versions | 10.0.23 |
| `oneuptime` | npm | All versions | 10.0.23 |

Products: Hackerbay Oneuptime.

## How do I fix CVE-2026-32598?

Upgrade oneuptime to 10.0.23 or later.

## Is CVE-2026-32598 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32598 exists.

## Other vulnerabilities in oneuptime

- [CVE-2026-33396](https://insights.sbomify.com/CVE-2026-33396/): Code injection in oneuptime (critical 10.0)
- [CVE-2026-32306](https://insights.sbomify.com/CVE-2026-32306/): OneUptime ClickHouse SQL Injection via Aggregate Query Parameters (critical 10.0)
- [CVE-2026-30956](https://insights.sbomify.com/CVE-2026-30956/): OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header (critical 10.0)
- [CVE-2026-30957](https://insights.sbomify.com/CVE-2026-30957/): OneUptime Synthetic Monitor RCE via exposed Playwright browser object (critical 10.0)
- [CVE-2026-30887](https://insights.sbomify.com/CVE-2026-30887/): OneUptime Affected by Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32598 and fix it if it is affected.

What it is: CVE-2026-32598 is a medium-severity vulnerability in oneuptime, published on 12 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32598 exists.

Affected packages and fixed versions:
- oneuptime (npm): affected all versions; fixed in 10.0.23
- oneuptime (npm): affected all versions; fixed in 10.0.23

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32598/ (Markdown: https://insights.sbomify.com/CVE-2026-32598/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32598
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32598
- OSV: https://osv.dev/vulnerability/CVE-2026-32598

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32598/
Summaries are generated and may contain mistakes; the official description above is the record.