Rancher: Improper Neutralization of Directives in Dynamically Evaluated Code
CVE-2026-44939 is a critical-severity improper neutralization of directives in dynamically evaluated code vulnerability in Rancher from SUSE, with a CVSS 4.0 base score of 9.4 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 2.14.2, 2.13.6, 2.12.10 as the first without the flaw, so updating Rancher to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.28% chance of exploitation within 30 days, higher than 70% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Rancher to 2.14.2 or 2.13.6 or 2.12.10 or 2.11.14, whichever matches your release line, or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| SUSE | Rancher | 2.14.0 up to, but not including, 2.14.2; 2.13.0 up to, but not including, 2.13.6; 2.12.0 up to, but not including, 2.12.10; 2.11.0 up to, but not including, 2.11.14; 2.10.0 up to, but not including, 2.10.12 | 2.14.2, 2.13.6, 2.12.10, 2.11.14, 2.10.12 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- NoneThe attack does not depend on a particular deployment or configuration.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- PassiveA user only needs to do something routine, such as viewing a page.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- HighSerious loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- HighSerious loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- HighSerious loss of availability on systems beyond the vulnerable one.
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA (suse.de).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Directives in Dynamically Evaluated Code
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. eval).
How developers prevent this class of flaw
- If possible, refactor your code so that it does not need to use eval() at all.
- For Python programs, it is frequently encouraged to use the ast.literal_eval() function instead of eval, since it is intentionally designed to avoid executing code. However, an adversary could still cause excessive memory or stack consumption via deeply nested structures, so the python documentation discourages use of ast.literal_eval() on untrusted data.
More Improper Neutralization of Directives in Dynamically Evaluated Code vulnerabilities (CWE-95)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Rancher
- 9.1 Critical severity
- 7.2 High severity
- 9.1 Critical severity
- 7.6 High severity
- 7.9 High severity
- 8.5 High severity
Recent Improper Neutralization of Directives in Dynamically Evaluated Code vulnerabilities
- 7.1 High severity
- 7.1 High severity
- 8.8 High severity
- 8.4 High severity
- 7.8 High severity
- 10.0 Critical severity
Spotted an error? Tell us.