Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-30957: OneUptime is a solution for monitoring and managing online services

57
This month
CRITICAL 9.9UPGRADE

CVE-2026-30957 is a critical-severity flaw (CVSS 9.9) affecting oneuptime. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 in

Why this priority

  • Critical severity
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score9.9 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance1.2% (top 31%)
CISA exploited listNo
WeaknessCWE-749
Published2026-03-10
Last modified2026-10-07
Publisher (CNA): GitHub, Inc. · Vendor: hackerbay

Share: LinkedIn · X · Reddit

Last updated 2026-10-07 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

hackerbay oneuptime UPGRADE
Affected: < 10.0.21
Fixed in: 10.0.21
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy oneuptime || rpm -q oneuptime || oneuptime --version
2. UPGRADE to 10.0.21 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade oneuptime
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade oneuptime
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Exact fixes by distribution

npm · @oneuptime/common · FIXED · 10.0.21 · vulnerable: < 10.0.21 · source
npm install @oneuptime/common@">=10.0.21" npm ls @oneuptime/common
Fedora 46 · python-hatchling · FIXED · 1.33.0-1.fc46 · FEDORA-2026-3ccbf17812 · source
sudo dnf upgrade --advisory=FEDORA-2026-3ccbf17812
Fedora ELN · pie · FIXED · 1.5.3-1.eln159 · FEDORA-2026-e009523caa · source
sudo dnf upgrade --advisory=FEDORA-2026-e009523caa

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-30957?

oneuptime: upgrade to 10.0.21. Exact commands for each OS are on this page.

Is CVE-2026-30957 being exploited?

CVE-2026-30957 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-30957 affect?

CVE-2026-30957 affects oneuptime. Severity is critical (CVSS 9.9). 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

How urgent is CVE-2026-30957?

Priority 57/100. Critical severity; Public exploit reference

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.