OneUptime has Synthetic Monitor RCE via exposed Playwright browser object
CVE-2026-30957GHSA-jw8q-gjvg-8w4q
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@oneuptime/common 10.0.21), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 10.0.21
- Fixed in
- 10.0.21
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-jw8q-gjvg-8w4q lists affected ranges: npm @oneuptime/common >=0 <10.0.21
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-jw8q-gjvg-8w4q lists affected ranges: npm @oneuptime/common >=0 <10.0.21 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- EPSS
- CVE-2026-30957: 1.22% estimated exploitation activity in the next 30 days; percentile 68.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary 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. Details A normal project member can create or edit monitors and monitor tests: - Monitor access control: https://github.com/OneUptime/oneuptime/blob/707bfd62e721a2845ee05b87cb5d3c611bda2276/Common/Models/DatabaseModels/Monitor.ts#L45-L70 - MonitorTest access control: https://github.com/OneUptime/oneuptime/blob/707bfd62e721a2845ee05b87cb5d3c611bda2276/Common/Models/DatabaseModels/MonitorTest.ts#L27-L52 The dashboard exposes a Playwright…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-jw8q-gjvg-8w4q
- Revision 2 · amended ·
Amended from osv record GHSA-jw8q-gjvg-8w4q
- Revision 1 · created ·
Published from ghsa record GHSA-jw8q-gjvg-8w4q
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-30957 Advisory: OneUptime has Synthetic Monitor RCE via exposed Playwright browser object IDs: CVE-2026-30957, GHSA-jw8q-gjvg-8w4q Record: https://patchnext.com/advisories/cve-2026-30957 (revision 3, source checked 26 Oct 2026, 12:43 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @oneuptime/common 10.0.21. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @oneuptime/common: affected < 10.0.21; fixed in 10.0.21 ## Suggested inspection (read-only) - `npm ls @oneuptime/common --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @oneuptime/common. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-jw8q-gjvg-8w4q (GitHub-reviewed advisory GHSA-jw8q-gjvg-8w4q lists affected ranges: npm @oneuptime/common >=0 <10.0.21) - Verified: https://osv.dev/vulnerability/GHSA-jw8q-gjvg-8w4q (OSV record GHSA-jw8q-gjvg-8w4q lists affected ranges: npm @oneuptime/common >=0 <10.0.21 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…