# 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.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Feb 2026
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-v264-xqh4-9xmm

## 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 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-27574?

2 open source packages ship an affected version, including @oneuptime/common. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@oneuptime/common` | npm | All versions | 10.0.0 |
| `@oneuptime/common` | npm | All versions | 10.0.0 |

Products: Hackerbay Oneuptime.

## How do I fix CVE-2026-27574?

Upgrade @oneuptime/common to 10.0.0 or later.

## 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:

- https://github.com/mbanyamer/CVE-2026-27574-OneUptime-RCE (github_poc): https://github.com/mbanyamer/CVE-2026-27574-OneUptime-RCE

## Other vulnerabilities in oneuptime

- [CVE-2026-33396](https://insights.sbomify.com/CVE-2026-33396/): Code injection in oneuptime (critical 10.0)
- [CVE-2026-32306](https://insights.sbomify.com/CVE-2026-32306/): OneUptime ClickHouse SQL Injection via Aggregate Query Parameters (critical 10.0)
- [CVE-2026-30956](https://insights.sbomify.com/CVE-2026-30956/): OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header (critical 10.0)
- [CVE-2026-30957](https://insights.sbomify.com/CVE-2026-30957/): OneUptime Synthetic Monitor RCE via exposed Playwright browser object (critical 10.0)
- [CVE-2026-30887](https://insights.sbomify.com/CVE-2026-30887/): OneUptime Affected by Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27574 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27574 exists.

Affected packages and fixed versions:
- @oneuptime/common (npm): affected all versions; fixed in 10.0.0
- @oneuptime/common (npm): affected all versions; fixed in 10.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-27574/ (Markdown: https://insights.sbomify.com/CVE-2026-27574/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27574
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27574
- OSV: https://osv.dev/vulnerability/CVE-2026-27574

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27574/
Summaries are generated and may contain mistakes; the official description above is the record.