Is CVE-2026-27574 actively exploited?

No active exploitation of CVE-2026-27574 has been confirmed so far. Continue monitoring, as exploit status can change.

Can CVE-2026-27574 be exploited remotely?

Yes. CVE-2026-27574 is exploitable remotely over the network (CVSS attack vector: Network).

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

CVE-2026-27574 has a CVSS score of 9.9 (CRITICAL) and an EPSS exploitation probability of 0.05%.

HOME VULNERABILITIESCVE-2026-27574

CRITICAL

CVE-2026-27574

CWE-94Published: February 21, 2026· Updated: Feb 23, 2026

9.9

CVSS v3.1

EPSS:0.05%probability of exploitation in 30 daysPercentile:15.1th

Official Description

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.

NVD Source

Technical Analysis

CVE-2026-27574 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.

Exploitation requires low privileges, which limits the exposure to scenarios where an attacker has already gained initial access.

A successful exploit results in complete confidentiality breach (data exposure), full integrity compromise (data manipulation), availability disruption (denial of service), with a CVSS base score of 9.9.

The vulnerability has a "Changed" scope, meaning successful exploitation can impact components beyond the vulnerable component itself — such as the host operating system or adjacent services.