CVE-2026-45102
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOneUptime 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOneUptime versions prior to 10.0.98 incorrectly use Node.js' vm module as a security isolation primitive. The vm module was not designed for sandboxing and can be escaped via manipulation of error objects or triggering infinite recursion, allowing attackers to break out of the intended isolation and potentially execute arbitrary code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed OneUptime versionCheck the package.json file or run 'npm list oneuptime' or check the version displayed in the OneUptime admin interfaceAffected if Version is lower than 10.0.98 (e.g., 10.0.97, 10.0.0, etc.)
-
Locate vm module usage in codebaseSearch source code for 'require('vm')' or 'import { vm }' statements, and review any files that import or use the vm moduleAffected if The vm module is imported and used in the codebase
-
Determine if vm is used for sandboxingReview files using vm module to check if vm.runInNewContext, vm.createContext, or similar functions are called to isolate untrusted codeAffected if vm functions are used to create isolated contexts for executing code (vm.runInNewContext, vm.createContext, etc.)
-
Check for error object manipulation vectorsReview any custom code handling vm errors or exceptions that could be manipulated to escape the vm sandboxAffected if Custom error handling exists around vm-isolated code execution
You are affected if your OneUptime version is prior to 10.0.98 AND your installation uses the Node.js vm module to isolate or sandbox untrusted code execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade OneUptime to version 10.0.98 or later. Additionally, review any custom code using the vm module and replace with proper sandboxing mechanisms such as containers, VMs, or security-focused sandbox libraries if the upgrade does not fully address the architectural misuse.
10.0.98
- 1. Backup your current OneUptime installation and database.
- 2. Check your current OneUptime version to confirm it is prior to 10.0.98.
- 3. Consult the official OneUptime upgrade documentation for your deployment method (Docker, Kubernetes, etc.).
- 4. Upgrade OneUptime to version 10.0.98 or later.
- 5. After upgrading, verify the Node.js vm module is no longer used for security isolation in your deployment.
- 6. Test that the monitoring and observability functionality works correctly after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45102 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45102 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data