CVE-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 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 v3 9.9 CRITICAL

9.9^/10

CVSS v3 : CRITICAL

Vector :

Exploitability : 3.1 / Impact : 6.0

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope CHANGED

References

Link	Resource
https://github.com/OneUptime/oneuptime/security/advisories/GHSA-h343-gg57-2q67	Exploit Vendor Advisory
https://github.com/OneUptime/oneuptime/security/advisories/GHSA-h343-gg57-2q67	Exploit Vendor Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:hackerbay:oneuptime:*:*:*:*:*:*:*:*

History

No history.

Information

Published : 2026-03-10 17:40

Updated : 2026-03-12 13:41

NVD link : CVE-2026-30887

Mitre link : CVE-2026-30887

CVE.ORG link : CVE-2026-30887

JSON object : View

Products Affected

hackerbay

oneuptime

CWE

CWE-94

Improper Control of Generation of Code ('Code Injection')

{"id": "CVE-2026-30887", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 9.9, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 3.1}]}, "published": "2026-03-10T17:40:14.887", "references": [{"url": "https://github.com/OneUptime/oneuptime/security/advisories/GHSA-h343-gg57-2q67", "tags": ["Exploit", "Vendor Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/OneUptime/oneuptime/security/advisories/GHSA-h343-gg57-2q67", "tags": ["Exploit", "Vendor Advisory"], "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-94"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "OneUptime es una soluci\u00f3n para monitorear y gestionar servicios en l\u00ednea. Antes de la versi\u00f3n 10.0.18, OneUptime permite a los miembros del proyecto ejecutar c\u00f3digo Playwright/JavaScript personalizado a trav\u00e9s de Monitores Sint\u00e9ticos para probar sitios web. Sin embargo, el sistema ejecuta este c\u00f3digo de usuario no confiable dentro del m\u00f3dulo vm inseguro de Node.js. Al aprovechar un escape est\u00e1ndar de la cadena de prototipos (this.constructor.constructor), un atacante puede eludir la sandbox, obtener acceso al objeto de proceso subyacente de Node.js y ejecutar comandos de sistema arbitrarios (RCE) en el contenedor oneuptime-probe. Adem\u00e1s, debido a que la sonda guarda las credenciales de la base de datos/cl\u00faster en sus variables de entorno, esto conduce directamente a un compromiso completo del cl\u00faster. Esta vulnerabilidad est\u00e1 corregida en la versi\u00f3n 10.0.18."}], "lastModified": "2026-03-12T13:41:22.380", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:hackerbay:oneuptime:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "CBDE45D3-FDDB-49A9-8065-4A95B2BBDEEF", "versionEndExcluding": "10.0.18"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}