---
title: "CVE-2026-30887: OneUpTime's Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE"
url: https://erroneo.us/security/cve/CVE-2026-30887/
description: "CVE-2026-30887 (@oneuptime/common (npm)): OneUptime is a solution for monitoring and managing online services. Prior to 10.0.18, OneUptime allows project…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-03-09
date_modified: 2026-03-10
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-30887"
kev: false
cvss: 10
epss: 0.00586
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-30887: OneUpTime's Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE

**Signal:** Critical, preconditions apply. Severe if exploited, but exploitation needs conditions that may not apply to you. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- Not in CISA KEV , but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.6% , percentile 47: FIRST’s model estimates a 0.6% chance of exploitation activity in the next 30 days, higher than 47% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Needs an account (low (any account)). Exposure depends on who can log in.
- Only applies if your dependency tree includes @oneuptime/common (npm) < 10.0.18, fixed in 10.0.18 . Check your lockfile, including transitive dependencies.

## What it is

OneUptime is a solution for monitoring and managing online services. Prior to 10.0.18, OneUptime allows project members to run custom Playwright/JavaScript code via Synthetic Monitors to test websites. However, the system executes this untrusted user code inside the insecure Node.js vm module. By leveraging a standard prototype-chain escape (this.constructor.constructor), an attacker can bypass the sandbox, gain access to the underlying Node.js process object, and execute arbitrary system commands (RCE) on the oneuptime-probe container. Furthermore, because the probe holds database/cluster credentials in its environment variables, this directly leads to a complete cluster compromise. This vulnerability is fixed in 10.0.18.

## Affected packages

- npm `@oneuptime/common` < 10.0.18 → fixed: 10.0.18

## Affected products (CVE record)

- OneUptime oneuptime: < 10.0.18

## Severity

- GitHub_M CVSS 3.1: 10 `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`
- GitHub CVSS 3.1: 9.9 `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc , automatable no , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.59% probability of exploitation activity in the next 30 days; percentile 47.

## Sources

- [GitHub Advisory GHSA-h343-gg57-2q67](https://github.com/advisories/GHSA-h343-gg57-2q67)
- [CVE.org record CVE-2026-30887](https://www.cve.org/CVERecord?id=CVE-2026-30887)
- [NVD entry CVE-2026-30887](https://nvd.nist.gov/vuln/detail/CVE-2026-30887)
- [github.com](https://github.com/OneUptime/oneuptime/security/advisories/GHSA-h343-gg57-2q67)

---
Source page: https://erroneo.us/security/cve/CVE-2026-30887/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt