CVE-2026-27728

OneUptime: OS Command Injection in Probe NetworkPathMonitor via unsanitized destination in traceroute exec()

Vulnerability type: OS Command Injection (CWE-78)

Who is impacted: Any authenticated user with the ability to create or edit a network path monitor in a OneUptime project can execute arbitrary operating system commands on the Probe server(s). In a multi-tenant SaaS deployment, this allows a malicious tenant to:

• Execute arbitrary commands as the Probe service user (Remote Code Execution)
• Read sensitive files from the Probe server (e.g., environment variables, credentials, service account tokens)
• Pivot to internal services accessible from the Probe's network position
• Compromise other tenants' monitoring data if Probes are shared across tenants
• Establish persistent backdoors (reverse shells, cron jobs, SSH keys)

Note: The NetworkPathMonitor class is fully implemented and exported but not yet wired into the monitor execution pipeline (no callers import it). The vulnerability will become exploitable once this monitor type is integrated. The code is present in the current codebase and ready to be activated.

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2026-27728 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (10.0.7); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-27728? CVE-2026-27728 is a critical-severity OS command injection vulnerability in @oneuptime/common (npm), affecting versions < 10.0.7. It is fixed in 10.0.7. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
2. How severe is CVE-2026-27728? CVE-2026-27728 has a CVSS score of 9.9 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @oneuptime/common are affected by CVE-2026-27728? @oneuptime/common (npm) versions < 10.0.7 is affected.
4. Is there a fix for CVE-2026-27728? Yes. CVE-2026-27728 is fixed in 10.0.7. Upgrade to this version or later.
5. Is CVE-2026-27728 exploitable, and should I be worried? Whether CVE-2026-27728 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-27728 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-27728? Upgrade @oneuptime/common to 10.0.7 or later.