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

Back
New CVE Detected

CVE-2026-58455 – Unauthenticated RCE via OS Command Injection – Dockwatch through 0.6.567

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-58455 is a critical unauthenticated OS command injection vulnerability in Dockwatch (by Notifiarr), a self-hosted Docker container management web UI, affecting all versions through 0.6.567. By chaining an authentication bypass with unsanitized shell command execution, remote attackers can inject and run arbitrary OS commands with no credentials or user interaction required. In the standard Dockwatch deployment — where the Docker socket is mounted — successful exploitation escapes the container and results in full host-level compromise.

Technical details

  • Root cause: Two weaknesses are exploited in sequence: (1) a missing exit; statement after an authentication redirect in loader.php (CWE-698: Execution After Redirect), which allows request processing to continue past the authentication gate; and (2) unsanitized user input passed directly to shell_exec() in ajax/compose.php (CWE-78: OS Command Injection).
  • Trigger conditions: An attacker first abuses the incomplete authentication check in loader.php to seed the required session flag, then sends a crafted HTTP POST request to ajax/compose.php with a malicious composePath parameter in the composePull action to inject arbitrary shell commands.
  • Attack vector: Fully network-accessible, requiring no authentication and no user interaction.
  • Impact: Arbitrary OS command execution on the underlying host. Because Dockwatch is standardly deployed with the Docker socket mounted, exploitation escapes the container and yields full host compromise, with complete confidentiality, integrity, and availability impact.

Affected software

  • Dockwatch (Notifiarr) — all versions through 0.6.567

Severity

  • CVSS v4.0 Base Score: 9.2 (Critical)
  • Vector: 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
  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • No patched release is currently available. A fix has been submitted via GitHub Pull Request #135 as of July 2, 2026, but has not yet been merged or released. The proposed patch adds the missing exit; call in loader.php and wraps the composePath parameter in escapeshellarg() across multiple compose actions in ajax/compose.php.
  • Immediate actions:
    • Remove internet exposure now — place the Dockwatch web UI behind a VPN or firewall and do not leave it publicly accessible until a patched version is released and applied.
    • If internet-facing access cannot be immediately restricted, consider taking the Dockwatch instance offline temporarily.
    • Monitor the Notifiarr/dockwatch repository for a patched release and apply it immediately upon availability.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge