Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.20% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-19444High confidence
Kubernetes kubectl cp path traversal on Windows allows arbitrary file writes
Kubernetes · Kubernetes
6.5MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Kubernetes Kubernetes and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 4 affected or under-investigation product states without a fixed product state in the same current advisory
Distribution package intelligence
4 package statesRelease-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | kubernetes | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian bookwormbookworm · source | kubernetes | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian forkyforky · source | kubernetes | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian sidsid · source | kubernetes | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-19444 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityk8s.io/kubectl: Kubernetes kubectl: Arbitrary file write via path traversal on Windows
The vendor explicitly identifies these products as affected by this CVE.
- dpu-kit-for-nvidia/must-gather-rhel10 as a component of DPU kit for NVIDIA
- multicluster-engine/registration-rhel9 as a component of Multicluster Engine for Kubernetes
- openshift-clients.src as a component of Red Hat OpenShift Container Platform 4
- openshift4/ose-cli-artifacts-rhel9 as a component of Red Hat OpenShift Container Platform 4
- Summary
- A flaw was found in Kubernetes kubectl. An attacker controlling a container can write arbitrary files to the host system when a user copies files from the container. Because the tool does not properly validate file paths when extracting archives on Windows, a malicious container can traverse directories and overwrite local files with the permissions of the user executing the command.
- Remediation
- This issue can be mitigated prior to upgrading by only using kubectl cp to copy files from containers whose contents are trusted, or by avoiding kubectl cp against untrusted containers when running the kubectl client on Windows.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
A path traversal vulnerability was discovered in the Kubernetes kubectl client's kubectl cp command on Windows. When copying files from a container, kubectl runs tar inside the container to build a tar archive, transfers it over the network, and unpacks it on the local machine. If the tar binary in the container is malicious, it can execute arbitrary code and emit unexpected output, allowing an attacker who controls container contents to write files to arbitrary paths on the user's local machine when kubectl cp is invoked, limited only by the system permissions of the local user. This issue only affects kubectl clients running on Windows.
What
A path traversal vulnerability was discovered in the Kubernetes kubectl client's kubectl cp command on Windows. When copying files from a container, kubectl runs tar inside the container to build a tar archive, transfers it over the network, and unpacks it on the local machine. If the tar binary in the container is malicious, it can execute arbitrary code and emit unexpected output, allowing an attacker who controls container contents to write files to arbitrary paths on the user's local machine when kubectl cp is invoked, limited only by the system permissions of the local user. This issue only affects kubectl clients running on Windows.
Why
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
How
An attacker operating through an adjacent network may attempt exploitation with elevated privileges. If successful, the issue may execute code or commands in the affected security context.
What
A path traversal vulnerability was discovered in the Kubernetes kubectl client's kubectl cp command on Windows. When copying files from a container, kubectl runs tar inside the container to build a tar archive, transfers it over the network, and unpacks it on the local machine. If the tar binary in the container is malicious, it can execute arbitrary code and emit unexpected output, allowing an attacker who controls container contents to write files to arbitrary paths on the user's local machine when kubectl cp is invoked, limited only by the system permissions of the local user. This issue only affects kubectl clients running on Windows.
Why
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
How
An attacker operating through an adjacent network may attempt exploitation with elevated privileges. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- an adjacent network → Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') → execute code or commands in the affected security context
- Attack surface
- Adjacent
- Privileges required
- High: elevated access is required
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-22 ↗
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:L/I:H/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CLowConfidentiality impact: A successful attack can cause a limited loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- dpu-kit-for-nvidia/must-gather-rhel10 as a component of DPU kit for NVIDIA
- multicluster-engine/registration-rhel9 as a component of Multicluster Engine for Kubernetes
- openshift-clients.src as a component of Red Hat OpenShift Container Platform 4
- openshift4/ose-cli-artifacts-rhel9 as a component of Red Hat OpenShift Container Platform 4
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- This issue can be mitigated prior to upgrading by only using kubectl cp to copy files from containers whose contents are trusted, or by avoiding kubectl cp against untrusted containers when running the kubectl client on Windows.
04
Evidence and provenance
Published 28 Sept 2026 · Last source change 28 Sept 2026, 18:09 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-29
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-88223
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- compliance/openshift-compliance-operator-bundle as a component of Compliance Operator; dpu-kit-for-nvidia/must-gather-rhel10 as a component of DPU kit for NVIDIA; multicluster-engine/cloudevents-conductor-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/cluster-api-provider-kubevirt-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/hive-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/must-gather-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/registration-rhel9 as a component of Multicluster Engine for Kubernetes; ocp-tools-4/jenkins-agent-base-rhel9 as a component of OpenShift Developer Tools and Services; ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services; openshift-lightspeed/openshift-mcp-server-rhel9 as a component of OpenShift Lightspeed; ansible-automation-platform-26/aap-must-gather-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/aap-must-gather-rhel9 as a component of Red Hat Ansible Automation Platform 2; openshift-gitops-1/argo-rollouts-rhel9 as a component of Red Hat OpenShift GitOps; openshift-gitops-1/argocd-agent-rhel9 as a component of Red Hat OpenShift GitOps; openshift-gitops-1/argocd-image-updater-rhel9 as a component of Red Hat OpenShift GitOps; openshift-gitops-1/gitops-rhel9-operator as a component of Red Hat OpenShift GitOps
- After
- dpu-kit-for-nvidia/must-gather-rhel10 as a component of DPU kit for NVIDIA; multicluster-engine/registration-rhel9 as a component of Multicluster Engine for Kubernetes; openshift-clients.src as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-cli-artifacts-rhel9 as a component of Red Hat OpenShift Container Platform 4
- ENISA EUVD mappingEUVD-2026-88223 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-88223"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.