Vulnerability in OneUptime (CVE-2026-32598)
Summary
Vulnerability in OneUptime (CVE-2026-32598). Confidential information can be exposed externally. Mitigation: upgrade to 10.0.24 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32598 has been found in OneUptime.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade OneUptime to 10.0.24 or later.
If unsure, ask your IT team or search "OneUptime CVE-2026-32598" on the vendor's site.
CVE-2026-32598 (OneUptime) — CWE-532 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 10.0.24 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-532) exists in OneUptime.
Check the vendor advisory for the affected versions of OneUptime.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 10.0.24.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'OneUptime' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'OneUptime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
OneUptimeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade OneUptime to 10.0.24ステージング環境で 10.0.24 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit security-advisories@github.com