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

New CVE Detected

CVE-2026-44939 – YAML Injection / Command Injection Leading to RCE and Container Escape – SUSE Ra…

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

Summary

CVE-2026-44939 is a critical command injection vulnerability in SUSE Rancher Manager affecting the cluster import endpoint /v3/import/{token}_{clusterId}.yaml. The flaw stems from the authImage query parameter being rendered without sanitization into a generated Kubernetes manifest template, allowing remote attackers to inject arbitrary YAML and execute malicious containers — effectively achieving remote code execution and container escape. The vulnerability carries a CVSS 4.0 score of 9.4 (Critical) and is exploitable over the network with no privileges required.

Technical details

  • Root cause: The authImage query parameter accepted by the cluster import endpoint is inserted directly into a Kubernetes manifest (YAML) template without input validation. Because YAML treats newlines as structural delimiters, an attacker can supply URL-encoded newline characters (%0A) to break out of the intended image field and inject arbitrary YAML keys and values into the rendered manifest.
  • Trigger conditions: An attacker must be able to send a crafted HTTP request to /v3/import/{token}_{clusterId}.yaml with a malicious authImage value. A cluster registration token is required to reach the endpoint; however, such tokens can be exposed through documentation, screenshots, or other channels.
  • Attack vector: Network-reachable, no authentication or privileges required (PR:N). The Rancher API (/v3/ family) is commonly exposed directly on the internet for multi-cluster management.
  • Impact: Successful exploitation enables full downstream cluster compromise, including: arbitrary code execution on control-plane nodes with elevated privileges; access to sensitive cluster secrets via the cattle service account; persistent attacker presence through deployed DaemonSets; and complete disruption of cluster operations.

Affected software

  • Rancher Manager 2.14.0 to < 2.14.2
  • Rancher Manager 2.13.0 to < 2.13.6
  • Rancher Manager 2.12.0 to < 2.12.10
  • Rancher Manager 2.11.0 to < 2.11.14
  • Rancher Manager 2.10.0 to < 2.10.12

Severity

CVSS v3.1 Base Score: 9.6 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

CVSS v4.0 Base Score: 9.4 (Critical)
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Mitigation and recommended actions

  • Immediate action — upgrade to a patched release:
    • Rancher 2.14.2 or later
    • Rancher 2.13.6 or later
    • Rancher 2.12.10 or later
    • Rancher 2.11.14 or later
    • Rancher 2.10.12 or later
  • The fix validates the authImage parameter to permit only valid OCI image reference characters, rejecting any input containing newlines, whitespace, or other characters capable of disrupting YAML syntax.
  • If immediate patching is not feasible, restrict network-level access to the Rancher API (/v3/import/ endpoint) to trusted IP ranges only, and ensure cluster registration tokens are not exposed publicly.

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