dbcve.org
OneuptimeApplication · Hackerbay

CVE-2026-27574

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

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. In versions 9.5.13 and below, custom JavaScript monitor feature uses Node.js's node:vm module (explicitly documented as not a security mechanism) to execute user-supplied code, allowing trivial sandbox escape via a well-known one-liner that grants full access to the underlying process. Because the probe runs with host networking and holds all cluster credentials (ONEUPTIME_SECRET, DATABASE_PASSWORD, REDIS_PASSWORD, CLICKHOUSE_PASSWORD) in its environment variables, and monitor creation is available to the lowest role (ProjectMember) with open registration enabled by default, any anonymous user can achieve full cluster compromise in about 30 seconds. This issue has been fixed in version 10.0.5.

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 versions 9.5.13 and below allow arbitrary code execution via the custom JavaScript monitor feature which uses Node.js's node:vm module (explicitly not a security mechanism). Attackers can trivially escape the sandbox to access environment variables containing all cluster credentials (ONEUPTIME_SECRET, DATABASE_PASSWORD, REDIS_PASSWORD, CLICKHOUSE_PASSWORD), achieving full cluster compromise.

MitigationImmediately upgrade to version 10.0.5 or later. As interim measures, disable open registration, restrict monitor creation permissions above ProjectMember role, and rotate all exposed credentials.

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

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 installed OneUptime version
    Check the package.json file in the OneUptime installation directory, or run a command like 'npm list oneuptime' or check the Docker image tag if running containers
    Affected if The version is below 10.0.5 (versions 9.5.13 and below are vulnerable)
  2. Verify Custom JavaScript monitor feature exists
    Look for the Custom JavaScript monitor functionality in the OneUptime admin panel or check the codebase for the monitor creation endpoint that uses the node:vm module
    Affected if The Custom JavaScript monitor feature is present and accessible to the user
  3. Check if open registration is enabled
    Examine the OneUptime authentication settings or configuration file for 'allowRegistration' or similar setting that permits self-service account creation
    Affected if Open registration is enabled, allowing unauthenticated attackers to create accounts
  4. Review monitor creation role permissions
    Inspect the OneUptime role-based access control settings to determine which roles can create custom JavaScript monitors
    Affected if ProjectMember role or lower can create custom JavaScript monitors, or no role restrictions exist

User is affected if running OneUptime version below 10.0.5 AND the Custom JavaScript monitor feature is accessible to authenticated users or open registration is enabled

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.5 or later
Fixed in 10.0.5
Vendor patch github.com →
Interim mitigation

Immediately upgrade to version 10.0.5 or later. As interim measures, disable open registration, restrict monitor creation permissions above ProjectMember role, and rotate all exposed credentials.

Recommended fix High confidence

10.0.5

  1. Backup your current OneUptime installation and database
  2. Stop the OneUptime services
  3. Upgrade to version 10.0.5 or later
  4. Verify the node:vm module is no longer used for user-supplied code execution
  5. Restart OneUptime services
  6. Validate that custom JavaScript monitors still function correctly
  7. Rotate all cluster credentials (ONEUPTIME_SECRET, DATABASE_PASSWORD, REDIS_PASSWORD, CLICKHOUSE_PASSWORD) as a precautionary measure since they may have been exposed

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

Fix this in Oneuptime Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
72.0 hours of engineering $12,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27574 — 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-27574 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