Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-59800 – Unauthenticated OS Command Injection (RCE) – 9Router before v0.4.44

Be the first to know when new zero-days emerge:

Summary

CVE-2026-59800 is a critical OS command injection vulnerability in 9Router (decolua/9router), an AI coding proxy designed for internet-facing VPS and cloud deployments, affecting all versions before 0.4.44. The vulnerability exists in the POST /api/tunnel/tailscale-install endpoint, which is absent from the application’s authentication middleware matcher, allowing any unauthenticated remote attacker to reach it and inject arbitrary shell commands. Rated 9.8 Critical (CVSS v3.1) and 9.2 Critical (CVSS v4.0), this vulnerability has been confirmed as actively exploited in the wild since July 4, 2026.

Technical details

  • Root cause (CWE-862 — Missing Authorization): The /api/tunnel/tailscale-install route is not included in the Next.js middleware matcher inside src/proxy.js, meaning dashboardGuard.proxy() is never invoked and no authentication check is applied to requests reaching this endpoint.
  • Root cause (CWE-78 — OS Command Injection): The endpoint reads a sudoPassword field from the JSON request body and writes it directly to the stdin of a sudo -S sh child process, alongside the body of the Tailscale install script. No sanitization or validation is performed on this input.
  • Trigger conditions: Exploitation succeeds when the 9Router Node.js process runs as root (the default in Docker images derived from node:* without a USER directive, or when installed globally via npm i -g as root), when NOPASSWD is configured for sudo, or when a valid sudo timestamp cache exists. All three conditions are common in typical self-hosted deployments.
  • Attack vector: A single unauthenticated HTTP POST request over the network; no credentials, user interaction, or prior access are required.
  • Impact: Full remote OS command execution on the host running 9Router, inheriting root privileges in the most common deployment configurations — enabling complete system takeover, data exfiltration, and lateral movement.
  • Active exploitation: The Shadowserver Foundation first observed exploitation evidence on July 4, 2026 (UTC), three days before CVE publication.

Affected software

  • 9router (npm package, vendor: decolua) — all versions before 0.4.44

Severity

  • CVSS v3.1 base score: 9.8 Critical
  • Vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 score: 9.2 Critical (CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)

Mitigation and recommended actions

  • Immediate: Upgrade 9router to version 0.4.44 or later, which moves the Tailscale install route inside the authenticated middleware matcher and removes the unauthenticated code execution path.
  • If immediate patching is not possible: Block external network access to the 9Router dashboard port (default: 20128) via firewall or network-level controls; restrict access to trusted IP ranges only.
  • Hardening: Ensure the 9Router Node.js process does not run as root — use a dedicated non-root user and avoid NOPASSWD sudo configurations.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge