CVE-2017-1002101

HIGHNVD 8.89.6▲
EchelonGraph scoreMEDIUM confidence

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 8.8; sources differ by 0.8.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 12%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with any volume type (including non-privileged pods, subject to file permissions) can access files/directories outside of the volume, including the host's filesystem.

CVSS v3
8.8
EG Score
9.6(medium)
EPSS
95.5%
KEV
Not listed

Published

March 13, 2018

Last Modified

November 21, 2024

References (8)

Vendor Advisories for CVE-2017-1002101(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatatomic-openshift-0:3.7.23-1.git.5.83efd71.el72018-03-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:43 UTCEPSS rescore
  2. 2026-07-12 05:43 UTCEPSS rescore
  3. 2026-07-11 08:24 UTCEPSS rescore
  4. 2026-07-09 19:06 UTCEPSS rescore
  5. 2026-07-08 15:10 UTCEPSS rescore
  6. 2026-07-07 13:42 UTCEPSS rescore
  7. 2026-07-06 16:24 UTCEPSS rescore
  8. 2026-07-06 16:24 UTCEPSS rescore
  9. 2026-07-05 02:27 UTCEPSS rescore
  10. 2026-07-04 11:56 UTCOSV refresh
  11. 2026-07-04 06:28 UTCEPSS rescore
  12. 2026-07-01 15:02 UTCEPSS rescore
  13. 2026-06-30 23:19 UTCEPSS rescore
  14. 2026-06-30 23:19 UTCEPSS rescore
  15. 2026-06-29 14:03 UTCEPSS rescore
  16. 2026-06-28 04:53 UTCEPSS rescore
  17. 2026-06-27 03:05 UTCEPSS rescore
  18. 2026-06-25 13:47 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-22 14:23 UTCEPSS rescore
  22. 2026-06-21 14:54 UTCEPSS rescore
  23. 2026-06-21 14:54 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
Show 37 more
  1. 2026-06-18 17:50 UTCEPSS rescore
  2. 2026-06-18 17:50 UTCEPSS rescore
  3. 2026-06-17 17:50 UTCEPSS rescore
  4. 2026-06-17 17:50 UTCEPSS rescore
  5. 2026-06-16 17:50 UTCEPSS rescore
  6. 2026-06-15 23:43 UTCOSV refresh
  7. 2026-06-15 17:45 UTCEPSS rescore
  8. 2026-06-14 23:14 UTCEPSS rescore
  9. 2026-06-14 23:14 UTCEPSS rescore
  10. 2026-06-13 22:57 UTCEPSS rescore
  11. 2026-06-13 22:57 UTCEPSS rescore
  12. 2026-06-12 23:09 UTCEPSS rescore
  13. 2026-06-11 13:57 UTCEPSS rescore
  14. 2026-06-07 15:22 UTCEPSS rescore
  15. 2026-06-07 15:22 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-06 13:45 UTCEPSS rescore
  18. 2026-06-05 22:44 UTCEPSS rescore
  19. 2026-06-05 06:08 UTCEPSS rescore
  20. 2026-06-05 06:08 UTCEPSS rescore
  21. 2026-06-04 13:10 UTCEPSS rescore
  22. 2026-06-04 13:10 UTCEPSS rescore
  23. 2026-06-02 20:10 UTCEPSS rescore
  24. 2026-05-31 22:28 UTCEPSS rescore
  25. 2026-05-31 22:28 UTCEPSS rescore
  26. 2026-05-31 00:14 UTCEPSS rescore
  27. 2026-05-29 13:41 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-28 13:42 UTCEPSS rescore
  30. 2026-05-28 10:33 UTCEG score recompute
  31. 2026-05-28 10:33 UTCVendor advisory
  32. 2026-05-28 10:33 UTCGHSA enrichment
  33. 2026-05-27 13:38 UTCEPSS rescore
  34. 2026-05-27 13:38 UTCEPSS rescore
  35. 2026-05-26 23:43 UTCOSV refresh
  36. 2026-05-26 07:17 UTCEPSS rescore
  37. 2026-05-24 16:44 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCbgeesaman/subpath-exploit
    First seen Mar 22, 2018

    Writeup of CVE-2017-1002101 with sample "exploit"/escape

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-1002101?
CVE-2017-1002101 is a high vulnerability published on March 13, 2018. In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with any volume type (including non-privileged pods, subject to file permissions) can access files/directories outside of the volume, including the host's…
When was CVE-2017-1002101 disclosed?
CVE-2017-1002101 was first published in the National Vulnerability Database on March 13, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-1002101 actively exploited?
CVE-2017-1002101 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-1002101?
CVE-2017-1002101 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.6.
How do I remediate CVE-2017-1002101?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-1002101, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-1002101

Explore →

Is Your Infrastructure Affected by CVE-2017-1002101?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs