dbcve.org
OneuptimeApplication · Hackerbay

CVE-2026-30957

CRITICAL · 9.9 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.21 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OneUptime Synthetic Monitors prior to 10.0.21 execute untrusted monitor code inside Node's vm module while exposing live Playwright browser and page objects to that code. A low-privileged authenticated user can call Playwright APIs on these exposed objects to spawn attacker-controlled executables on the probe server/container, achieving server-side RCE without needing a separate vm sandbox escape.

MitigationUpgrade OneUptime to version 10.0.21 or later, which properly isolates the synthetic monitor code from the Playwright browser APIs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OneuptimeApplication
Affected:< 10.0.21

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OneUptime installation and version
    Locate the OneUptime installation (e.g., check docker containers, node_modules, or package.json) and determine the installed version number
    Affected if Version is below 10.0.21
  2. Verify Synthetic Monitors feature is enabled
    Check if the Synthetic Monitors module/feature is active in the OneUptime deployment (look for monitor configurations, scheduled tasks, or related API endpoints)
    Affected if Synthetic Monitors feature is enabled and running
  3. Confirm user access to monitor code execution
    Examine whether low-privileged authenticated users can create or modify synthetic monitor scripts that get executed via the vm module
    Affected if Low-privileged users can submit or modify monitor code that gets executed with Playwright objects in scope
  4. Inspect vm module usage with Playwright exposure
    Review the synthetic monitor execution code to verify if monitor scripts are run using Node's vm module while having live browser/page objects available in the execution context
    Affected if Monitor code executes in vm module with exposed Playwright browser/page objects

A user is affected if running OneUptime version below 10.0.21 with Synthetic Monitors enabled, where monitor code runs in the vm module with direct access to Playwright browser APIs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.21 or later
Fixed in 10.0.21
Interim mitigation

Upgrade OneUptime to version 10.0.21 or later, which properly isolates the synthetic monitor code from the Playwright browser APIs.

Recommended fix High confidence

OneUptime version 10.0.21

  1. Upgrade OneUptime to version 10.0.21 or later to address the arbitrary command execution vulnerability in Synthetic Monitors
  2. After upgrading, verify that Synthetic Monitors functionality remains operational
  3. Confirm the fix by testing that Synthetic Monitor code no longer has access to the exposed Playwright browser/page objects in the vm context

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Oneuptime Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,960
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,536.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30957 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30957 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data