Remote code execution via Node VM sandbox escape
Published Feb 21, 2026 · Updated Feb 21, 2026
Code injection in OneUptime before 10.0.5 allows remote authenticated users to execute commands through custom JavaScript monitors. VMRunner.ts passes project-supplied monitor scripts to vm.runInContext in Node.js's node:vm module, letting constructor-chain code reach process and invoke commands in the probe. ProjectMember access is sufficient, and default open registration lets remote attackers obtain that role; execution exposes cluster credentials and the probe's network reach.
Summary
What happened
Code injection in OneUptime before 10.0.5 allows remote authenticated users to execute commands through custom JavaScript monitors. VMRunner.ts passes project-supplied monitor scripts to vm.runInContext in Node.js's node:vm module, letting constructor-chain code reach process and invoke commands in the probe. ProjectMember access is sufficient, and default open registration lets remote attackers obtain that role; execution exposes cluster credentials and the probe's network reach.
The record
- CVE
- CVE-2026-27574
- Published
- Feb 21, 2026
- Updated
- Feb 21, 2026
- Vendor
- OneUptime
- Product
- OneUptime
- Classifications
- CWE-94, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 21, 2026CVE publishedPublication date reported by the CVE source.
- Feb 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 10.0.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory node:vm escape proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo