Skip to main content

Oneuptime CVE-2026-30921

CRITICAL
Exposed Dangerous Method or Function (CWE-749)
2026-03-10 security-advisories@github.com GHSA-4j36-39gm-8vq8
9.9
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged project user
  2. Exploit
    Submit malicious Playwright code to Synthetic Monitor
  3. Execution
    Execute arbitrary code via injected browser object
  4. Impact
    Compromise oneuptime-probe service and beyond

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Dangerous method exposure prevention
Exploitation Conditions

Low-privileged project user account with access to OneUptime Synthetic Monitors feature. Custom Playwright code execution capability must be enabled in the probe service. OneUptime versions prior to 10.0.20.

Impact

CVSS 9.9 with PoC. Second OneUptime vulnerability.

Exploit ScenarioDerived

An attacker uses the exposed synthetic monitoring functionality to execute arbitrary code.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

OneUptime prior to 10.0.20 exposes dangerous functionality in Synthetic monitoring that enables code execution.

Earlier versions of this analysis (1)
v1 Mar 12, 2026 - 21:55 CVSS 9.9

Exposed dangerous functionality in OneUptime Synthetic monitoring enables RCE.

RemediationAI

Update OneUptime.

Affected Packages

npm @oneuptime/common fix: 10.0.20

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

OneUptime < 10.0.20 has a CWE-749 exposed dangerous method in Synthetic monitoring.

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

GitHub Advisory PRIMARY 9.9 CRITICAL
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
PoC Detected
Mar 12, 2026 - 13:44 vuln.today
Public exploit code
CVE Published
Mar 10, 2026 - 17:40 nvd
CRITICAL 9.9

DescriptionGitHub Advisory

OneUptime is a solution for monitoring and managing online services. Prior to 10.0.20, OneUptime Synthetic Monitors allow low-privileged project users to submit custom Playwright code that is executed on the oneuptime-probe service. In the current implementation, this untrusted code is run inside Node's vm and is given live host Playwright objects such as browser and page. This creates a distinct server-side RCE primitive: the attacker does not need the classic this.constructor.constructor(...) sandbox escape. Instead, the attacker can directly use the injected Playwright browser object to reach browser.browserType().launch(...) and spawn an arbitrary executable on the probe host/container. This vulnerability is fixed in 10.0.20.

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 1 npm packages depend on @oneuptime/common (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 10.0.20.

Executive ViewAI

Why It Matters

OneUptime Synthetic Monitors contain a critical remote code execution vulnerability (CVSS 9.9) that allows low-privileged users to execute arbitrary code on monitoring infrastructure. Organizations using OneUptime versions prior to 10.0.20 face immediate risk of system compromise, data breach, and operational disruption through the probe service.

Business Impact: Severe
Compensating Controls

Disable custom Playwright code submission in synthetic monitors until patch available; implement WAF rules to block synthetic monitor API endpoints from untrusted sources; segment probe services on isolated network with restricted egress; restrict OneUptime user roles to prevent project-level synthetic monitor creation; require administrative approval for any custom monitor code; monitor and log all Playwright code execution attempts; implement file integrity monitoring on probe service executables.

Threat Intelligence Overview

EPSS Score
0.0%
Top 97% exploitable
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Very High

Priority Score

70
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +50
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Affected Products (CPE)GitHub Advisory

cpe:2.3:a:hackerbay:oneuptime:*:*:*:*:*:*:*:*
CVE-2026-27728 CRITICAL POC
9.9 Feb 25

OS command injection in OneUptime monitoring platform before 10.0.7. Authenticated users can execute arbitrary commands

CVE-2026-30957 CRITICAL POC
9.9 Mar 10

OneUptime prior to 10.0.21 has a fourth vulnerability in Synthetic monitoring exposing dangerous functionality.

CVE-2026-27574 CRITICAL POC
9.9 Feb 21

Code injection in OneUptime monitoring via custom JS monitor using vm module. PoC and patch available.

CVE-2026-30956 CRITICAL POC
9.9 Mar 10

OneUptime prior to 10.0.21 has a third authorization bypass enabling low-privileged users to access admin functions.

CVE-2025-65966 HIGH POC
8.8 Nov 26

OneUptime is a solution for monitoring and managing online services. Rated high severity (CVSS 8.8), this vulnerability

CVE-2026-30958 HIGH POC
8.6 Mar 10

Unauthenticated path traversal in OneUptime prior to 10.0.21 lets remote attackers read arbitrary files from the server

CVE-2024-29194 HIGH POC
8.3 Mar 24

OneUptime is a solution for monitoring and managing online services. Rated high severity (CVSS 8.3), this vulnerability

CVE-2026-28787 HIGH POC
8.2 Mar 06

OneUptime versions 10.0.11 and earlier contain an improper WebAuthn implementation where server-side challenge validatio

CVE-2025-66028 MEDIUM POC
6.9 Nov 26

OneUptime is a solution for monitoring and managing online services. Rated medium severity (CVSS 6.9), this vulnerabilit

CVE-2026-33396 CRITICAL
9.9 Mar 26

Remote command execution can be achieved by low-privileged authenticated users (ProjectMember role) in OneUptime monitor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy