Critical severity · published Mar 9, 2026
CVE-2026-30887
OneUptime Affected by Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE
9.9
CVSS
0.4%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Changed
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 35% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
ON
oneuptime · OneUptime
< 10.0.18 · source: vendor, NVD
Affected product
ON
oneuptime
OneUptime
More from oneuptime
9.9
CVE-2026-45102
OneUptime: RCE due to Node.js' vm module escape via error objects and infinite recursion
9.9
CVE-2026-33396
OneUptime has sandbox escape in Synthetic Monitor Playwright runtime allows project members to execute arbitrary commands on Probe
9.9
CVE-2026-32306
OneUptime ClickHouse SQL Injection via Aggregate Query Parameters
9.9
CVE-2026-30957
OneUptime Synthetic Monitor RCE via exposed Playwright browser object
9.9
CVE-2026-30956
OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header