Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.9amended

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

CVE-2026-27728GHSA-jmhp-5558-qxh5

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@oneuptime/common 10.0.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-27728: 1.97% estimated exploitation activity in the next 30 days; percentile 80.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary An OS command injection vulnerability in NetworkPathMonitor.performTraceroute() allows any authenticated project user to execute arbitrary operating system commands on the Probe server by injecting shell metacharacters into a monitor's destination field. Details The vulnerability exists in Probe/Utils/Monitors/MonitorTypes/NetworkPathMonitor.ts, lines 149–191. The performTraceroute() method constructs a shell command by directly interpolating the user-controlled destination parameter into a string template, then executes it via childprocess.exec() (wrapped through promisify): The destination value originates from the public trace() method (line 31), which accepts URL | Hostname | IPv4 | IPv6 | string types. When a raw string is passed (line 47: hostAddress = destination), no validation or sanitization is performed before it reaches performTraceroute(). childprocess.exec() spawns a shell (/bin/sh), so any shell metacharacters (;, |, $(), , &&, ||, \n) in destination will be…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-jmhp-5558-qxh5

  2. Revision 2 · amended ·

    Amended from osv record GHSA-jmhp-5558-qxh5

  3. Revision 1 · created ·

    Published from ghsa record GHSA-jmhp-5558-qxh5

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27728

Advisory: OneUptime: OS Command Injection in Probe NetworkPathMonitor via unsanitized destination in traceroute exec()
IDs: CVE-2026-27728, GHSA-jmhp-5558-qxh5
Record: https://patchnext.com/advisories/cve-2026-27728 (revision 3, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @oneuptime/common 10.0.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @oneuptime/common: affected < 10.0.7; fixed in 10.0.7

## Suggested inspection (read-only)
- `npm ls @oneuptime/common --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @oneuptime/common.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jmhp-5558-qxh5 (GitHub-reviewed advisory GHSA-jmhp-5558-qxh5 lists affected ranges: npm @oneuptime/common >=0 <10.0.7)
- Verified: https://osv.dev/vulnerability/GHSA-jmhp-5558-qxh5 (OSV record GHSA-jmhp-5558-qxh5 lists affected ranges: npm @oneuptime/common >=0 <10.0.7 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…