CVE-2026-27574 OneUptime: node:vm sandbox escape in probe allows any project member to achieve RCE
An attacker can execute arbitrary code and compromise the cluster by exploiting a sandbox escape in the custom JavaScript monitor feature.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-27574?
CVE-2026-27574 is a critical code injection vulnerability in oneuptime, published on 21 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-94
Which versions are affected by CVE-2026-27574?
2 open source packages ship an affected version, including @oneuptime/common. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
@oneuptime/common npm | All versions | 10.0.0 |
@oneuptime/common npm | All versions | 10.0.0 |
Products include Hackerbay Oneuptime.
How do I fix CVE-2026-27574?
Upgrade @oneuptime/common to 10.0.0 or later.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
Is CVE-2026-27574 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27574 exists.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in oneuptime
- CVE-2026-33396 Code injection in oneuptime
- CVE-2026-32306 OneUptime ClickHouse SQL Injection via Aggregate Query Parameters
- CVE-2026-30956 OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header
- CVE-2026-30957 OneUptime Synthetic Monitor RCE via exposed Playwright browser object
- CVE-2026-30887 OneUptime Affected by Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE
Sources
Also known as GHSA-v264-xqh4-9xmm.