| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-h343-gg57-2q67 | OneUpTime's Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 10 Mar 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Oneuptime
Oneuptime oneuptime |
|
| Vendors & Products |
Oneuptime
Oneuptime oneuptime |
|
| Metrics |
ssvc
|
Mon, 09 Mar 2026 23:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | OneUptime Affected by Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE | |
| Weaknesses | CWE-94 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-10T14:00:44.197Z
Reserved: 2026-03-06T00:04:56.700Z
Link: CVE-2026-30887
Updated: 2026-03-10T14:00:32.517Z
Status : Received
Published: 2026-03-10T17:40:14.887
Modified: 2026-03-10T18:18:51.113
Link: CVE-2026-30887
No data.
OpenCVE Enrichment
Updated: 2026-03-10T14:06:29Z
Github GHSA