Quick answers
- Is CVE-2026-32598 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32598 being exploited in the wild.
- How severe is CVE-2026-32598?
- Medium severity, with a CVSS score of 6.5, published 13 March 2026.
- Which products and versions are affected?
- OneUptime all versions up to 10.0.23.
- Is there a fix for CVE-2026-32598?
- A patch was published on 2026-03-13: Fixed in version 10.0.24 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-32598 attacked?
- It is attacked with local access, in a web application.
- Am I affected by CVE-2026-32598?
- Check whether you run Hackerbay Oneuptime or OneUptime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a sensitive information disclosure (CWE-532) in the password reset flow. The vulnerable code in App/FeatureSet/Identity/API/Authentication.ts (lines 370-371) logs the complete password reset URL containing the plaintext token via logger.info(). This log level is enabled by default in production and persists to stdout, log files, and any configured log aggregation systems. The attack requires only read access to application logs—no authentication or network traversal is needed beyond accessing the logging infrastructure. An attacker can extract the plaintext token, then call the reset-password API endpoint with the stolen token to reset the victim's password. Additionally, login credentials (including cleartext passwords) are logged at DEBUG level (line 909), which is commonly enabled during incident troubleshooting. The vulnerability affects all versions of OneUptime up to and including 10.0.23 and is patched in 10.0.24.
Affected products
- OneUptime oneuptime all versions up to 10.0.23
Identifiers
- CVE-2026-32598
- GHSA-4524-cj9j-g4fj
Timeline
- 2026-03-13: disclosed: Advisory published
- 2026-03-13: patched: Fixed in version 10.0.24