OneUptime
OneUptime: node:vm sandbox escape in probe allows any project member to achieve RCE
OneUptime is a solution for monitoring and managing online services. In versions 9.5.13 and below, custom JavaScript monitor feature uses Node.js's node:vm module (explicitly documented as not a security mechanism) to execute user-supplied code, allowing trivial sandbox escape via a well-known one-liner that grants full access to the underlying process. Because the probe runs with host networking and holds all cluster credentials (ONEUPTIME_SECRET, DATABASE_PASSWORD, REDIS_PASSWORD, CLICKHOUSE_PASSWORD) in its environment variables, and monitor creation is available to the lowest role (ProjectMember) with open registration enabled by default, any anonymous user can achieve full cluster compromise in about 30 seconds. This issue has been fixed in version 10.0.5.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 10.0.5
Fixed in 10.0.5
Mitigation
Upgrade oneuptime to 10.0.5 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 6 h after publication; not in CISA KEV. First PoC: mbanyamer/CVE-2026-27574-OneUptime-RCE (created 21 Feb 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| mbanyamer/CVE-2026-27574-OneUptime-RCE | 21 Feb 2026 +6 h | 1 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.