Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as ProjectMember
-
DeliveryCreate malicious Synthetic Monitor
-
ExploitAccess unblocked _browserType property
-
ExecutionLaunch browser process with arbitrary commands
-
ImpactExecute code on Probe host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires authenticated access as ProjectMember role in OneUptime versions prior to 10.0.35. Attacker must create or modify a Synthetic Monitor with malicious Playwright script code exploiting unblocked _browserType and launchServer properties to execute arbitrary commands on the Probe container. |
| Impact | This represents a critical real-world risk based on multiple converging signals. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) indicates network-accessible exploitation with low complexity, requiring only low-privileged authenticated access, no user interaction, and resulting in complete confidentiality, integrity, and availability compromise with scope change beyond the vulnerable component. SSVC framework assessment confirms proof-of-concept exploit availability, non-automatable exploitation, and total technical impact. While the vulnerability requires authenticated ProjectMember credentials (PR:L), the attack complexity is low and a POC exists, significantly lowering the exploitation barrier. No CISA KEV listing indicates no confirmed active exploitation at time of analysis, but the combination of critical CVSS score, POC availability, and the prevalence of monitoring platforms in production environments makes this a high-priority patching target. The scope change (S:C) is particularly concerning as compromise of the monitoring infrastructure could provide lateral movement opportunities across monitored systems. |
| Exploit ScenarioDerived | A malicious insider or compromised ProjectMember account holder creates a synthetic monitor with a Playwright script containing code that traverses page.context().browser()._browserType.launchServer() to spawn a reverse shell or execute arbitrary commands on the Probe container host. The attacker leverages network access (AV:N) with low complexity (AC:L) and no user interaction required (UI:N), achieving complete system compromise. Publicly available exploit code exists per SSVC framework data, lowering the technical barrier for exploitation and enabling rapid weaponization by threat actors with access to low-privileged credentials. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 26, 2026
Remote command execution can be achieved by low-privileged authenticated users (ProjectMember role) in OneUptime monitoring platform versions prior to 10.0.35 by exploiting incomplete sandbox restrictions in Synthetic Monitor Playwright script execution. Attackers can traverse the unblocked _browserType and launchServer properties via page.context().browser()._browserType.launchServer() to spawn arbitrary processes on the Probe container or host. A proof-of-concept exploit exists per SSVC framework data, and the vulnerability carries a CVSS score of 9.9 with Critical severity due to scope change and total technical impact.
RemediationAI
Upgrade OneUptime to version 10.0.35 or later, which contains the vendor-released patch addressing the sandbox escape vulnerability (see GitHub security advisory at https://github.com/OneUptime/oneuptime/security/advisories/GHSA-cqpg-phpp-9jjg and patch commit e8e4ee3ff0740eb131045ab3d67453141c46178a). Organizations unable to immediately upgrade should restrict ProjectMember role assignments to only highly trusted users, implement strict network segmentation to isolate Probe containers from sensitive infrastructure, and monitor Probe container process execution for suspicious launchServer invocations or unexpected child processes. Review and audit all existing synthetic monitor scripts for potentially malicious code, and consider temporarily disabling synthetic monitoring features until patching is complete if the risk tolerance permits operational impact.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
OneUptime (CPE: cpe:2.3:a:oneuptime:oneuptime:*:*:*:*:*:*:*:*) is an open-source monitoring and observability platform that executes synthetic monitor scripts using Playwright automation framework. The vulnerability stems from improper neutralization of special elements used in OS commands (CWE-78). The VMRunner.runCodeInNodeVM function executes user-supplied code with access to a live Playwright page object, relying on a denylist-based sandbox to restrict dangerous operations. However, the denylist fails to block the _browserType internal property and launchServer method, allowing attackers to escape the sandbox by traversing from the page context through the browser object hierarchy to invoke launchServer, which can spawn arbitrary system processes with the privileges of the Probe container or host.
Know when Oneuptime gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
3DescriptionCVE.org
OneUptime is an open-source monitoring and observability platform. Prior to version 10.0.35, a low-privileged authenticated user (ProjectMember) can achieve remote command execution on the Probe container/host by abusing Synthetic Monitor Playwright script execution. Synthetic monitor code is executed in VMRunner.runCodeInNodeVM with a live Playwright page object in context. The sandbox relies on a denylist of blocked properties/methods, but it is incomplete. Specifically, _browserType and launchServer are not blocked, so attacker code can traverse page.context().browser()._browserType.launchServer(...) and spawn arbitrary processes. Version 10.0.35 contains a patch.
Executive ViewAI
OneUptime monitoring platform versions before 10.0.35 allow authenticated low-privileged users to execute arbitrary commands on Probe containers and underlying hosts through sandbox escape in Synthetic Monitor scripts, creating an immediate path for lateral movement and infrastructure compromise. Organizations using OneUptime for monitoring face direct risk of attackers escalating from limited project member roles to full system control without administrator intervention.
Vendor-released patch: OneUptime 10.0.35 or later. If upgrade cannot occur within 7 days: restrict ProjectMember role creation and script upload permissions to trusted users only; implement network segmentation to limit Probe container egress; enable audit logging on all Synthetic Monitor executions; monitor Probe process creation for unexpected child processes (launchServer spawned processes).
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
OS command injection in OneUptime monitoring platform before 10.0.7. Authenticated users can execute arbitrary commands
OneUptime prior to 10.0.21 has a fourth vulnerability in Synthetic monitoring exposing dangerous functionality.
Code injection in OneUptime monitoring via custom JS monitor using vm module. PoC and patch available.
OneUptime monitoring platform prior to 10.0.18 allows code injection (CVSS 9.9) enabling RCE through the monitoring conf
OneUptime prior to 10.0.21 has a third authorization bypass enabling low-privileged users to access admin functions.
OneUptime prior to 10.0.20 exposes dangerous functionality in Synthetic monitoring that enables code execution.
OneUptime is a solution for monitoring and managing online services. Rated high severity (CVSS 8.8), this vulnerability
Unauthenticated path traversal in OneUptime prior to 10.0.21 lets remote attackers read arbitrary files from the server
OneUptime versions prior to 10.0.19 allow unauthenticated attackers to hijack GitHub App integrations across projects by
OneUptime is a solution for monitoring and managing online services. Rated high severity (CVSS 8.3), this vulnerability
OneUptime versions 10.0.11 and earlier contain an improper WebAuthn implementation where server-side challenge validatio
OneUptime is a solution for monitoring and managing online services. Rated medium severity (CVSS 6.9), this vulnerabilit
EUVD-2026-16189
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB