dbcve.org
CWE-95Weakness · CWE-95

CVE-2026-44939

CRITICAL · 9.4 CVSS v4.0 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in Rancher Manager's cluster import endpoint (/v3/import/{token}_{clusterId}.yaml) where unsanitized YAML parameters allow remote attackers to inject and execute arbitrary commands. This can enable container escape, letting attackers break out of isolated containers and execute malicious code on the underlying host system.

MitigationUpgrade Rancher Manager to version 2.14.2 or later, which contains proper sanitization of YAML parameters in the cluster import endpoint to prevent command injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Rancher Manager installation
    Run 'helm list -A' or check for Rancher pods in the cluster using 'kubectl get pods -A | grep -i rancher'
    Affected if Rancher Manager is not installed in the environment, the system is not affected by this CVE
  2. Determine installed Rancher version
    Check the Rancher deployment version: 'kubectl get deployment rancher -n cattle-system -o jsonpath='{.spec.template.spec.containers[0].image}'' or via Helm 'helm list -n cattle-system'
    Affected if The installed version is lower than 2.14.2 and falls within earlier 2.x release lines, indicating vulnerability to this CVE
  3. Verify cluster import functionality is enabled
    Check if the Rancher import controller is active: 'kubectl get clusters -A' and look for imported clusters, or inspect Rancher API endpoints for /v3/import availability
    Affected if The cluster import feature is actively enabled and accessible, creating the attack surface for this vulnerability
  4. Audit for unauthorized cluster imports
    Review Rancher cluster list for unexpected imported clusters: 'kubectl get clusters -A' and check Rancher UI for unknown imported clusters that may indicate exploitation
    Affected if Unexpected or unauthorized imported clusters exist that were not provisioned by legitimate administrators, suggesting possible exploitation
  5. Check for suspicious YAML import configurations
    Review any recent import YAML files or configurations submitted to the /v3/import endpoint, checking for anomalous command or payload patterns in logs
    Affected if Import YAML files contain unexpected shell commands, script injections, or malicious payloads that indicate command injection has occurred

A system is affected if Rancher Manager versions below 2.14.2 are running with the cluster import endpoint accessible and no evidence of compromise is found.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Rancher Manager to version 2.14.2 or later, which contains proper sanitization of YAML parameters in the cluster import endpoint to prevent command injection.

Recommended fix Moderate confidence

Rancher Manager 2.14.2

  1. Upgrade Rancher Manager to version 2.14.2 or later to address the command injection vulnerability
  2. Verify the upgrade by reviewing the Rancher release notes for version 2.14.2
  3. Test the upgrade in a non-production environment before deploying to production
  4. After upgrade, verify the /v3/import endpoint no longer allows command injection through YAML parameters
  5. Ensure all imported clusters use the updated Rancher Manager for cluster management
Caveat Review Rancher 2.14.2 release notes for any breaking changes or deprecations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44939 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44939 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data