CVE-2019-1002101
A public proof of concept exists; no exploitation attested.
- Published2019-04-01
- Fixed in1.13.5 · 1.12.7 · 1.11.9
- WeaknessCWE-59
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The kubectl cp command allows copying files between containers and the user machine. To copy files from a container, Kubernetes creates a tar inside the container, copies it over the network, and kubectl unpacks it on the user’s machine. If the tar binary in the container is malicious, it could run any code and output unexpected, malicious results. An attacker could use this to write files to any path on the user’s machine when kubectl cp is called, limited only by the system permissions of the local user. The untar function can both create and follow symbolic links. The issue is resolved in kubectl v1.11.9, v1.12.7, v1.13.5, and v1.14.0.
Timeline
dates in UTC- 2019-04-0114:29CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-1002101?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-1002101?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.13 | ≥ 1.13.0, < 1.13.5 | 1.13.5 | NVD · OSV |
| 1.12 | ≥ 1.12.0, < 1.12.7 | 1.12.7 | NVD · OSV |
| 1.11 | ≥ 1.11.0, < 1.11.9 | 1.11.9 | NVD |
| 1.11 | < 1.11.9 | 1.11.9 | OSV |
| 1.14 | = 1.14.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.9 | = 3.9 | no fix published | NVD |
| 3.10 | = 3.10 | no fix published | NVD |
| 3.11 | = 3.11 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Kubernetes to 1.13.5 · 1.12.7 · 1.11.9
Advisories and patches
- github.comPatch
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 1 repository, unverifiedbrompwnie/CVE-2019-1002101-Helpers PoC-in-GitHub
Sources
- CNACVSS 3.06.4read 2026-10-23
- NVDCVSS 3.05.5read 2026-10-23
- NVDCVSS 2.05.8read 2026-10-23
- NVDweakness (CWE)CWE-59read 2026-10-23
- FIRST EPSSEPSS score12.8 %read 2026-10-23
- PoC-in-GitHubproof of concept1read 2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
- Published
- 2019-04-01
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-1002101?
Is CVE-2019-1002101 actively exploited?
What is the CVSS score for CVE-2019-1002101?
Running k8s.io/kubernetes? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.