Skip to main content

Oneuptime CVE-2026-27574

CRITICAL
Code Injection (CWE-94)
2026-02-21 security-advisories@github.com GHSA-v264-xqh4-9xmm
9.9
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege user
  2. Delivery
    Create custom JavaScript monitor
  3. Exploit
    Insert sandbox escape payload
  4. Execution
    Execute arbitrary code in probe process
  5. Impact
    Access cluster credentials from environment

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

OneUptime versions 9.5.13 and below with custom JavaScript monitor feature enabled. Requires valid user account with Project role (lowest privilege). Probe must run with host networking and contain ONEUPTIME_SECRET, DATABASE_PASSWORD, REDIS_PASSWORD, CLICKHOUSE_PASSWORD in environment variables.

Impact

CVSS 9.9.

Exploit ScenarioDerived

Inject code via custom JS monitor for RCE.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Code injection in OneUptime monitoring via custom JS monitor using vm module. PoC and patch available.

Earlier versions of this analysis (1)
v1 Mar 12, 2026 - 22:04 CVSS 9.9

Code injection in OneUptime JS monitor.

RemediationAI

Update OneUptime.

Affected Packages

npm @oneuptime/common fix: 10.0.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-94 using Node.js vm module (not sandboxed).

Know when Oneuptime gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 9.9 CRITICAL
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
PoC Detected
Feb 23, 2026 - 20:36 vuln.today
Public exploit code
Patch released
Feb 23, 2026 - 20:36 nvd
Patch available
CVE Published
Feb 21, 2026 - 11:15 nvd
CRITICAL 9.9

DescriptionGitHub Advisory

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.

Executive ViewAI

Why It Matters

A critical vulnerability (CVSS 9.9) in OneUptime monitoring infrastructure could allow attackers to gain complete control of affected systems and the services they monitor. Organizations using OneUptime for service monitoring face potential widespread outage visibility loss and operational disruption if exploited.

Business Impact: Severe
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 83% exploitable
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Very High

Priority Score

70
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +50
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Affected Products (CPE)GitHub Advisory

cpe:2.3:a:hackerbay:oneuptime:*:*:*:*:*:*:*:*
CVE-2026-27728 CRITICAL POC
9.9 Feb 25

OS command injection in OneUptime monitoring platform before 10.0.7. Authenticated users can execute arbitrary commands

CVE-2026-30957 CRITICAL POC
9.9 Mar 10

OneUptime prior to 10.0.21 has a fourth vulnerability in Synthetic monitoring exposing dangerous functionality.

CVE-2026-30887 CRITICAL POC
9.9 Mar 10

OneUptime monitoring platform prior to 10.0.18 allows code injection (CVSS 9.9) enabling RCE through the monitoring conf

CVE-2026-30956 CRITICAL POC
9.9 Mar 10

OneUptime prior to 10.0.21 has a third authorization bypass enabling low-privileged users to access admin functions.

CVE-2026-30921 CRITICAL POC
9.9 Mar 10

OneUptime prior to 10.0.20 exposes dangerous functionality in Synthetic monitoring that enables code execution.

CVE-2025-65966 HIGH POC
8.8 Nov 26

OneUptime is a solution for monitoring and managing online services. Rated high severity (CVSS 8.8), this vulnerability

CVE-2026-30958 HIGH POC
8.6 Mar 10

Unauthenticated path traversal in OneUptime prior to 10.0.21 lets remote attackers read arbitrary files from the server

CVE-2026-30920 HIGH POC
8.6 Mar 10

OneUptime versions prior to 10.0.19 allow unauthenticated attackers to hijack GitHub App integrations across projects by

CVE-2024-29194 HIGH POC
8.3 Mar 24

OneUptime is a solution for monitoring and managing online services. Rated high severity (CVSS 8.3), this vulnerability

CVE-2026-28787 HIGH POC
8.2 Mar 06

OneUptime versions 10.0.11 and earlier contain an improper WebAuthn implementation where server-side challenge validatio

CVE-2025-66028 MEDIUM POC
6.9 Nov 26

OneUptime is a solution for monitoring and managing online services. Rated medium severity (CVSS 6.9), this vulnerabilit

CVE-2026-33396 CRITICAL
9.9 Mar 26

Remote command execution can be achieved by low-privileged authenticated users (ProjectMember role) in OneUptime monitor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy