Vulnerability in OneUptime (CVE-2026-45102)
Summary
Vulnerability in OneUptime (CVE-2026-45102). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 10.0.98 or later.
Original description
The description as published by the source.
OneUptime is an open-source monitoring and observability platform. Prior to 10.0.98, OneUptime uses the Node.js' vm module as an isolation primitive. This API was not designed for that and can be escaped via error objects and infinite recursion. This vulnerability is fixed in 10.0.98.
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-45102 has been found in OneUptime.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade OneUptime to 10.0.98 or later.
If unsure, ask your IT team or search "OneUptime CVE-2026-45102" on the vendor's site.
CVE-2026-45102 (OneUptime) — CWE-693 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Patched: 10.0.98 — 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-693) exists in OneUptime.
Check the vendor advisory for the affected versions of OneUptime.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 10.0.98.
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.98ステージング環境で 10.0.98 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com