How severe is CVE-2026-44939?

No CVSS score has been assigned to CVE-2026-44939 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-44939?

CVE-2026-44939 affects the following packages: github.com/rancher/rancher (Go), github.com/rancher/rancher (Go), github.com/rancher/rancher (Go), github.com/rancher/rancher (Go), github.com/rancher/rancher (Go), github.com/rancher/rancher (Go). Ecosystems affected: Go.

How do I fix CVE-2026-44939?

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.

How do I detect CVE-2026-44939 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2026-44939 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-44939?

O3 pinpoints whether CVE-2026-44939 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2026-44939 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-44939 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2026-44939?

CVE-2026-44939 is classified as CWE-95 (CWE-95). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-44939 published, and has it been updated?

CVE-2026-44939 was published on June 19, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-44939

CVE-2026-44939 is a CWE-95 vulnerability in github.com/rancher/rancher. O3 Security confirms whether CVE-2026-44939 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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 Aug 12, 2026 · OSV.dev, NVD, 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

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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/rancher/rancher`	≥ 2.14.0&&< 2.14.2	2.14.2
🐹Go	`github.com/rancher/rancher`	≥ 2.13.0&&< 2.13.6	2.13.6
🐹Go	`github.com/rancher/rancher`	≥ 2.12.0&&< 2.12.10	2.12.10
🐹Go	`github.com/rancher/rancher`	≥ 2.11.0&&< 2.11.14	2.11.14
🐹Go	`github.com/rancher/rancher`	≥ 2.10.0&&< 2.10.12	2.10.12
🐹Go	`github.com/rancher/rancher`	all versions	0.0.0-20260617231817-2aa77eb283e7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-44939 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-44939. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-44939 in your dependencies?

O3 detects CVE-2026-44939 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works