CVE-2026-44939GHSA-MHC6-2GFQ-XX62GO-2026-5875
Command injection through unsanitized YAML parameter in Rancher
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.14.2, 2.13.6, 2.12.10, 2.11.14, 2.10.12, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A command injection vulnerability in the Rancher Manager cluster before 2.14.2 import endpoint /v3/import/{token}_{clusterId}.yaml through unsanitized YAML parameters could allow remote attackers to break out of an image, and execute e.g. malicious containers.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Rancher
From 2.14.0 · fixed in 2.14.2; From 2.13.0 · fixed in 2.13.6; From 2.12.0 · fixed in 2.12.10; From 2.11.0 · fixed in 2.11.14; From 2.10.0 · fixed in 2.10.12
- github.com/rancher/rancherGo
From 2.14.0 · fixed in 2.14.2
- github.com/rancher/rancherGo
From 2.13.0 · fixed in 2.13.6
- github.com/rancher/rancherGo
From 2.12.0 · fixed in 2.12.10
- github.com/rancher/rancherGo
From 2.11.0 · fixed in 2.11.14
- github.com/rancher/rancherGo
From 2.10.0 · fixed in 2.10.12
- github.com/rancher/rancherGo
fixed in 0.0.0-20260617231817-2aa77eb283e7