What is the CVSS score of CVE-2026-30957?

CVE-2026-30957 has a CVSS 3.1 base score of 9.9 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

Is there a public PoC exploit available for CVE-2026-30957?

Yes, a public proof-of-concept exploit is available for CVE-2026-30957. Prioritise patching immediately. EPSS: 0.3%.

How to fix or mitigate CVE-2026-30957?

Within 24 hours: Inventory all OneUptime deployments and identify which versions are in use; disable Synthetic Monitors feature if operationally feasible and restrict access to the OneUptime platform to essential personnel only. Within 7 days: Implement network segmentation to isolate OneUptime probe servers from critical systems; apply restrictive RBAC to limit low-privileged user access to monitoring functions; deploy WAF rules to monitor and block suspicious command injection patterns. Within 30 days: Upgrade to OneUptime 10.0.21 or later when patch becomes available; conduct forensic review of probe server logs for signs of exploitation; reset credentials for all OneUptime service accounts.

Oneuptime CVE-2026-30957

Q: Which versions of Oneuptime are affected by CVE-2026-30957?

A critical vulnerability in OneUptime Synthetic Monitors (CVE-2026-30957) allows authenticated users with low privileges to execute arbitrary commands on probe servers, potentially compromising…. A patch is available.

CRITICAL

Exposed Dangerous Method or Function (CWE-749)

2026-03-10 security-advisories@github.com

GHSA-jw8q-gjvg-8w4q

RCE Oneuptime Hackerbay

9.9

CVSS 3.1 · Vendor: github

View

Attack ChainAIDerived

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

Access

Authenticate as low-privileged project user
Exploit

Create malicious Synthetic Monitor
Execution

Inject code accessing exposed Playwright objects
Impact

Execute arbitrary commands on probe server

Vulnerability Assessment

Weakness	CWE CWE-749 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V8 - Authorization Dangerous method exposure prevention
Exploitation Conditions	Low-privileged authenticated project user account required. OneUptime Synthetic Monitors feature must be enabled with vm module executing untrusted monitor code while exposing live Playwright browser/page objects to the execution context.
Impact	CVSS 9.9 with PoC.
Exploit ScenarioDerived	Exploitation through synthetic monitoring.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.

Patch available 0.3% 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.21 has a fourth vulnerability in Synthetic monitoring exposing dangerous functionality.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:55 CVSS 9.9

Fourth OneUptime vulnerability in Synthetic monitoring.

RemediationAI

Update OneUptime. All four vulnerabilities must be patched.

Affected Packages

npm @oneuptime/common fix: 10.0.21

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

CWE-749 in OneUptime < 10.0.21.

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

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (github) PRIMARY 9.9 CRITICAL

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from Vendor (github) · only source for this CVE.

CVSS VectorVendor: github

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

PoC Detected

Mar 12, 2026 - 14:11 vuln.today

Public exploit code

CVE Published

Mar 10, 2026 - 18:18 nvd

CRITICAL 9.9

DescriptionCVE.org

OneUptime is a solution for monitoring and managing online services. Prior to 10.0.21, OneUptime Synthetic Monitors allow a low-privileged authenticated project user to execute arbitrary commands on the oneuptime-probe server/container. The root cause is that untrusted Synthetic Monitor code is executed inside Node's vm while live host-realm Playwright browser and page objects are exposed to it. A malicious user can call Playwright APIs on the injected browser object and cause the probe to spawn an attacker-controlled executable. This is a server-side remote code execution issue. It does not require a separate vm sandbox escape. This vulnerability is fixed in 10.0.21.

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.21.

Executive ViewAI

Why It Matters

A critical vulnerability in OneUptime Synthetic Monitors (CVE-2026-30957) allows authenticated users with low privileges to execute arbitrary commands on probe servers, potentially compromising monitoring infrastructure and enabling lateral movement into your environment. This poses an immediate risk to organizations using OneUptime versions prior to 10.0.21, as public exploits are already available.

Business Impact: Severe

Compensating Controls

Restrict network access to OneUptime probe servers using firewalls and network segmentation; implement least-privilege access controls to limit which users can create or modify Synthetic Monitors; deploy host-based intrusion detection on probe servers; monitor probe server processes and network connections for anomalous activity; disable Synthetic Monitors feature entirely if not critical to operations; consider deploying a WAF in front of OneUptime to detect and block command injection attempts; implement container runtime security monitoring on probe containers to detect unauthorized command execution.

Threat Intelligence Overview

EPSS Score

0.3%

Top 50% exploitable

Exploit

POC

Public exploit code exists

Data Quality

5 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

VulDB

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.3%

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.