Quick answers
- Is CVE-2026-15687 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15687 being exploited in the wild.
- How severe is CVE-2026-15687?
- Low severity, with a CVSS score of 2.4, published 23 July 2026.
- Which products and versions are affected?
- Kubernetes Java-Client >= 10.0.0, < 25.0.1; 26.0.0.
- Is there a fix for CVE-2026-15687?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-15687 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-15687?
- Check whether you run Kubernetes Java-Client 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 (CWE-22) exists in the Kubernetes Java client library's `copyDirectoryFromPod` method. When the `enableTarCompressing` parameter is set to `false` (often done for distroless containers), the library fails to properly validate file paths sent from the pod. A compromised pod can exploit this during a copy operation to create files in arbitrary locations on the client machine. The attack requires the client to initiate a copy operation from a pod controlled by the attacker and requires high privileges (PR:H) and user interaction (UI:R). The issue is fixed in versions 25.0.1, 26.0.1, and 27.0.0.
Affected products
- Kubernetes java-client >= 10.0.0, < 25.0.1; 26.0.0
Timeline
- 2026-07-22: disclosed: Issue reported on GitHub
- 2026-07-23: advisory: CVE published to NVD