Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go
Not in CISA KEV

CVE-2026-44939 — rancher

Fix: rancher/rancher@2aa77eb

CVE-2026-44939 is a CWE-95 vulnerability in github.com/rancher/rancher. A fix is available for github.com/rancher/rancher — see the affected versions and patch details below.

Command injection through unsanitized YAML parameter in Rancher

Also known asGHSA-mhc6-2gfq-xx62GO-2026-5875
Published
Jun 19, 2026
Updated
Aug 12, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-44939.

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

6 pkgs affected
🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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:

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/rancher/rancher≥ 2.14.0&&< 2.14.22.14.2go get github.com/rancher/rancher@v2.14.2
🐹Gogithub.com/rancher/rancher≥ 2.13.0&&< 2.13.62.13.6go get github.com/rancher/rancher@v2.13.6
🐹Gogithub.com/rancher/rancher≥ 2.12.0&&< 2.12.102.12.10go get github.com/rancher/rancher@v2.12.10
🐹Gogithub.com/rancher/rancher≥ 2.11.0&&< 2.11.142.11.14go get github.com/rancher/rancher@v2.11.14
🐹Gogithub.com/rancher/rancher≥ 2.10.0&&< 2.10.122.10.12go get github.com/rancher/rancher@v2.10.12
🐹Gogithub.com/rancher/rancherall versions0.0.0-20260617231817-2aa77eb283e7go get github.com/rancher/rancher@v0.0.0-20260617231817-2aa77eb283e7

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/rancher/rancher to 2.14.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44939 is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### 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
O3 Security · Impact-Aware SCA

Is CVE-2026-44939 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2026-44939: rancher RCE | O3 Security