github.com/rancher/rancher

CVE-2026-44939

CVE-2026-44939 is a critical-severity security vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.14.0, < 2.14.2. It is fixed in 2.14.2, 2.13.6, 2.12.10, 2.11.14, 2.10.12, 0.0.0-20260617231817-2aa77eb283e7.

Key facts
CVSS score
9.6
Critical
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
github.com/rancher/rancher
Fixed in
2.14.2, 2.13.6, 2.12.10, 2.11.14, 2.10.12, 0.0.0-20260617231817-2aa77eb283e7
Disclosed
2026

Summary

Impact A critical command injection vulnerability has been identified in the Rancher Manager cluster import endpoint /v3/import/{token}_{clusterId}.yaml through unsanitized YAML parameters. This endpoint accepts an authImage query parameter that is rendered without sanitization into a generated Kubernetes manifest template. By including URL-encoded newlines in the parameter value, an attacker can break out of the image: field to inject arbitrary YAML keys and malicious configurations, such as commands to execute malicious containers. Exploitation of this vulnerability requires the following conditions to be met: Attackers must obtain a valid cluster registration token (these tokens may be exposed, for example, through documentation, screenshots, or insecure communication channels). The victim’s cluster operator must execute kubectl apply against a maliciously crafted URL. When a victim applies this compromised manifest using kubectl apply, a DaemonSet is deployed with the injected configuration. This DaemonSet: Runs on all control-plane nodes with hostNetwork: true enabled. Uses the cattle service account, which possesses cluster-admin privileges. Mounts /etc/kubernetes directly from the host. Executes attacker-controlled commands via the injected command: field. An attacker who successfully exploits this vulnerability could: Achieve full control over downstream Kubernetes clusters. Execute arbitrary code on control-plane nodes with elevated privileges. Access sensitive cluster secrets and configurations via the privileged service account. Disrupt cluster operations by manipulating critical control-plane workloads. Establish persistent access through the deployed DaemonSet. Note: If you believe that you might have been impacted by this vulnerability, it's highly advised to review your clusters' logs and deployment logs for signs of malicious deployments and to rotate all service accounts and credentials that might have been exposed in such a scenario. Please refer to the associated MITRE ATT&CK - Technique - Deploy Container for further information about this category of attack. Patches This vulnerability is addressed by validating the authImage parameter to ensure it contains only valid OCI image reference characters, rejecting any input containing newlines, whitespace, or other characters that could break YAML syntax. Patched versions of Rancher include release v2.14.2, v2.13.6, v2.12.10, v2.11.14 and v2.10.12. Workarounds If upgrading to a patched version immediately is not feasible, users are encouraged to apply the following workaround: Review the kube-api-auth DaemonSet: Inspect downstream clusters for the kube-api-auth DaemonSet within the cattle-system namespace (which targets control-plane nodes). Review this resource configuration carefully for: Unexpected command: or args: fields in the container specification. References to non-standard or suspicious container images. Any modifications occurring after the initial cluster import. Validate manifest integrity: Before running kubectl apply on any import manifests, verify that the source URLs originate from trusted sources and match expected patterns. Credits This security issue was reported by the following collaborators according to our responsible disclosure policy: Radisauskas Arnoldas from NATO and the NATO Cyber Security Centre (NCSC). Michael Wollner from Deutsche Telekom AG. References If you have any questions or comments about this advisory: Reach out to the SUSE Rancher Security team for security related inquiries. Open an issue in the Rancher repository. Verify with our support matrix and product support lifecycle.

Impact

Severity and exposure

CVE-2026-44939 has a CVSS score of 9.6 (Critical). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (2.14.2, 2.13.6, 2.12.10, 2.11.14, 2.10.12, 0.0.0-20260617231817-2aa77eb283e7). Upgrading removes the vulnerable code path.

Affected versions

go

  • github.com/rancher/rancher (>= 2.14.0, < 2.14.2)
  • github.com/rancher/rancher (>= 2.13.0, < 2.13.6)
  • github.com/rancher/rancher (>= 2.12.0, < 2.12.10)
  • github.com/rancher/rancher (>= 2.11.0, < 2.11.14)
  • github.com/rancher/rancher (>= 2.10.0, < 2.10.12)
  • github.com/rancher/rancher (< 0.0.0-20260617231817-2aa77eb283e7)

Security releases

  • github.com/rancher/rancher → 2.14.2 (go)
  • github.com/rancher/rancher → 2.13.6 (go)
  • github.com/rancher/rancher → 2.12.10 (go)
  • github.com/rancher/rancher → 2.11.14 (go)
  • github.com/rancher/rancher → 2.10.12 (go)
  • github.com/rancher/rancher → 0.0.0-20260617231817-2aa77eb283e7 (go)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-44939 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-44939 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-44939 in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade github.com/rancher/rancher to 2.14.2 or later
  • Upgrade github.com/rancher/rancher to 2.13.6 or later
  • Upgrade github.com/rancher/rancher to 2.12.10 or later
  • Upgrade github.com/rancher/rancher to 2.11.14 or later
  • Upgrade github.com/rancher/rancher to 2.10.12 or later
  • Upgrade github.com/rancher/rancher to 0.0.0-20260617231817-2aa77eb283e7 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-44939

What is CVE-2026-44939?

CVE-2026-44939 is a critical-severity security vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.14.0, < 2.14.2. It is fixed in 2.14.2, 2.13.6, 2.12.10, 2.11.14, 2.10.12, 0.0.0-20260617231817-2aa77eb283e7.

How severe is CVE-2026-44939?

CVE-2026-44939 has a CVSS score of 9.6 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/rancher/rancher are affected by CVE-2026-44939?

github.com/rancher/rancher (go) versions >= 2.14.0, < 2.14.2 is affected.

Is there a fix for CVE-2026-44939?

Yes. CVE-2026-44939 is fixed in 2.14.2, 2.13.6, 2.12.10, 2.11.14, 2.10.12, 0.0.0-20260617231817-2aa77eb283e7. Upgrade to this version or later.

Is CVE-2026-44939 exploitable, and should I be worried?

Whether CVE-2026-44939 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-44939 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-44939?
  • Upgrade github.com/rancher/rancher to 2.14.2 or later
  • Upgrade github.com/rancher/rancher to 2.13.6 or later
  • Upgrade github.com/rancher/rancher to 2.12.10 or later
  • Upgrade github.com/rancher/rancher to 2.11.14 or later
  • Upgrade github.com/rancher/rancher to 2.10.12 or later
  • Upgrade github.com/rancher/rancher to 0.0.0-20260617231817-2aa77eb283e7 or later

Stop the waste.
Protect your environment with Kodem.