Is CVE-2026-19444 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-19444 being exploited in the wild.

How severe is CVE-2026-19444?

Medium severity, with a CVSS score of 6.5, published 28 September 2026.

Which products and versions are affected?

Kubernetes Kubectl v1.34.0 to v1.34.11, v1.35.0 to v1.35.8, v1.36.0 to v1.36.4.

Is there a fix for CVE-2026-19444?

A patch was published on 2026-08-12: Fix merged for windows backslash escaping in kubectl cp Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-19444 attacked?

It is attacked from the adjacent network.

Am I affected by CVE-2026-19444?

Check whether you run Kubernetes Kubectl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-19444: Kubernetes kubectl path traversal on Windows in cp command

CVE-2026-19444 · Severity: medium · CVSS 6.5 · Published 2026-09-28

A vulnerability in the Kubernetes kubectl cp command allows attackers to write files to arbitrary locations on Windows machines. When copying files from a container, kubectl uses a tar binary inside the container; if that binary is malicious or controlled by an attacker, it can write files anywhere on the user's system. This could lead to code execution, credential theft, or system compromise on the local machine.

Vendors: Kubernetes.

Quick answers

Is CVE-2026-19444 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-19444 being exploited in the wild.
How severe is CVE-2026-19444?: Medium severity, with a CVSS score of 6.5, published 28 September 2026.
Which products and versions are affected?: Kubernetes Kubectl v1.34.0 to v1.34.11, v1.35.0 to v1.35.8, v1.36.0 to v1.36.4.
Is there a fix for CVE-2026-19444?: A patch was published on 2026-08-12: Fix merged for windows backslash escaping in kubectl cp Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-19444 attacked?: It is attacked from the adjacent network.
Am I affected by CVE-2026-19444?: Check whether you run Kubernetes Kubectl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A path traversal vulnerability in kubectl cp on Windows fails to properly validate or escape backslash characters when extracting tar archives from containers. An attacker controlling container contents can craft a malicious tar archive that, when unpacked by an unprivileged kubectl process, writes files to arbitrary paths outside the intended directory. The vulnerability requires the user to invoke kubectl cp from a container under attacker control, but affects all Windows kubectl clients in versions 1.34.0–1.34.11, 1.35.0–1.35.8, and 1.36.0–1.36.4; patches are available.

Affected products

Kubernetes kubectl v1.34.0 to v1.34.11, v1.35.0 to v1.35.8, v1.36.0 to v1.36.4

Timeline

2026-09-28: disclosed: CVE-2026-19444 publicly disclosed
2026-08-12: patched: Fix merged for windows backslash escaping in kubectl cp

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.