CVE-2026-30887
published 2026-03-10CVE-2026-30887: OneUptime is a solution for monitoring and managing online services. Prior to 10.0.18, OneUptime allows project members to run custom Playwright/JavaScript…
PriorityP270critical9.9CVSS 3.1
AVNACLPRLUINSCCHIHAH
EPSS
0.39%
30.6th percentile
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
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| hackerbay | oneuptime | < 10.0.18 | 10.0.18 |
| oneuptime | common | >= 0 < 10.0.18 | 10.0.18 |
| oneuptime | oneuptime | < 10.0.18 | 10.0.18 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
OneUpTime's Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE
ghsa·2026-03-07
CVE-2026-30887 [CRITICAL] CWE-94 OneUpTime's Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE
OneUpTime's Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE
### Summary
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.
### Details
The root cause of the vulnerability exists in [Common/Server/Utils/VM/V
OSV
OneUpTime's Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE
osv·2026-03-07
CVE-2026-30887 [CRITICAL] OneUpTime's Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE
OneUpTime's Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE
### Summary
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.
### Details
The root cause of the vulnerability exists in [Common/Server/Utils/VM/V
No detection rules found.
No public exploits indexed.
2026-03-10
Published