Vulnerability 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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Hackerbay | Oneuptime | < 10.0.5 |
Related Weaknesses (CWE)
References
- https://github.com/OneUptime/oneuptime/commit/7f9ed4d43945574702a26b7c206e38cc34Patch
- https://github.com/OneUptime/oneuptime/security/advisories/GHSA-v264-xqh4-9xmmExploitVendor Advisory
FAQ
What is CVE-2026-27574?
CVE-2026-27574 is a vulnerability with a CVSS score of 9.9 (CRITICAL). 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 secur...
How severe is CVE-2026-27574?
CVE-2026-27574 has been rated CRITICAL with a CVSS base score of 9.9/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-27574?
Check the references section above for vendor advisories and patch information. Affected products include: Hackerbay Oneuptime.