CVE-2026-17106

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the ApplyLayer helpers) do not confine filesystem operations to the destination directory. The extractor decides where each archive entry lands using lexical string checks and then performs the filesystem operation on a path that is resolved by the OS, so links introduced by the archive can be followed out of the destination directory. An attacker who controls the contents of an archive can create or overwrite files at arbitrary paths writable by the extracting process.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
48(Track*)
EG Risk 48/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 18, 2026

Last Modified

August 28, 2026

Advisory Details (6)

Auto-updated Aug 18, 2026
Patch available. Sources: github, github_release.
github_release Patch Available

v0.3.0

Patch available: moby/go-archive v0.3.0

https://github.com/moby/go-archive/releases/tag/v0.3.0
github_release Patch Available

v5.4.0

Patch available: docker/compose v5.4.0

https://github.com/docker/compose/releases/tag/v5.4.0
generic

Docker Engine version 29 release notes | Docker Docs

https://docs.docker.com/engine/release-notes/29/#2970
github_release Patch Available

v0.38.0

Patch available: docker/sbx-releases v0.38.0

https://github.com/docker/sbx-releases/releases/tag/v0.38.0
generic

Docker Desktop release notes | Docker Docs

https://docs.docker.com/desktop/release-notes/#4860
github Patch Available

Crafted tar archive can write outside the extraction directory · Advisory · moby/go-archive · GitHub

https://github.com/moby/go-archive/security/advisories/GHSA-hfg8-hc9c-6c3h

Vendor Advisories for CVE-2026-17106(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift-logging/cluster-logging-rhel9-operator:17884395052026-09-10redhat
redhatpodman-main-6.0.2-2.2.hum12026-08-10redhat

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.

Affected Packages

(2 across 2 ecosystems)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-github-moby-go-archive0.2.0-10.3.3-1—
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/moby/go-archive—0.3.0—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 26× in last 7d / 82× 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-09-18 23:32 UTCEG score recompute
  2. 2026-09-18 23:32 UTCVendor advisory
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-18 12:41 UTCVendor advisory
  5. 2026-09-18 01:42 UTCEG score recompute
  6. 2026-09-18 01:42 UTCVendor advisory
  7. 2026-09-17 14:51 UTCVendor advisory
  8. 2026-09-17 03:43 UTCVendor advisory
  9. 2026-09-16 15:58 UTCEG score recompute
  10. 2026-09-16 15:58 UTCVendor advisory
  11. 2026-09-16 14:07 UTCEPSS rescore
  12. 2026-09-16 05:14 UTCEPSS rescore
  13. 2026-09-16 04:51 UTCVendor advisory
  14. 2026-09-15 17:27 UTCVendor advisory
  15. 2026-09-15 06:34 UTCEG score recompute
  16. 2026-09-15 06:34 UTCVendor advisory
  17. 2026-09-14 19:43 UTCVendor advisory
  18. 2026-09-14 06:54 UTCVendor advisory
  19. 2026-09-13 20:03 UTCEG score recompute
  20. 2026-09-13 20:03 UTCVendor advisory
  21. 2026-09-13 16:46 UTCEPSS rescore
  22. 2026-09-13 09:11 UTCVendor advisory
  23. 2026-09-12 22:21 UTCEG score recompute
  24. 2026-09-12 22:21 UTCVendor advisory
  25. 2026-09-12 15:00 UTCEPSS rescore
Show 65 more
  1. 2026-09-12 11:30 UTCVendor advisory
  2. 2026-09-12 00:04 UTCEG score recompute
  3. 2026-09-12 00:04 UTCVendor advisory
  4. 2026-09-11 14:52 UTCEPSS rescore
  5. 2026-09-11 13:13 UTCEG score recompute
  6. 2026-09-11 13:13 UTCVendor advisory
  7. 2026-09-11 09:36 UTCEPSS rescore
  8. 2026-09-11 00:38 UTCVendor advisory
  9. 2026-09-10 12:53 UTCEG score recompute
  10. 2026-09-10 12:53 UTCVendor advisory
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-10 02:03 UTCVendor advisory
  13. 2026-09-09 15:12 UTCVendor advisory
  14. 2026-09-09 03:24 UTCEG score recompute
  15. 2026-09-09 03:24 UTCVendor advisory
  16. 2026-09-08 22:00 UTCEPSS rescore
  17. 2026-09-08 02:59 UTCVendor advisory
  18. 2026-09-07 16:08 UTCVendor advisory
  19. 2026-09-07 01:16 UTCVendor advisory
  20. 2026-09-06 14:26 UTCEG score recompute
  21. 2026-09-06 14:26 UTCVendor advisory
  22. 2026-09-06 13:47 UTCEPSS rescore
  23. 2026-09-06 03:35 UTCVendor advisory
  24. 2026-09-05 16:44 UTCEG score recompute
  25. 2026-09-05 16:44 UTCVendor advisory
  26. 2026-09-05 05:52 UTCVendor advisory
  27. 2026-09-04 19:01 UTCEG score recompute
  28. 2026-09-04 19:01 UTCVendor advisory
  29. 2026-09-04 07:48 UTCEG score recompute
  30. 2026-09-04 07:48 UTCVendor advisory
  31. 2026-09-04 05:06 UTCEPSS rescore
  32. 2026-09-03 19:51 UTCVendor advisory
  33. 2026-09-02 21:56 UTCEG score recompute
  34. 2026-09-02 14:11 UTCEPSS rescore
  35. 2026-09-01 20:16 UTCEG score recompute
  36. 2026-09-01 13:53 UTCEPSS rescore
  37. 2026-09-01 09:25 UTCEG score recompute
  38. 2026-09-01 04:39 UTCEPSS rescore
  39. 2026-08-30 23:16 UTCEG score recompute
  40. 2026-08-30 19:17 UTCEPSS rescore
  41. 2026-08-30 01:29 UTCEG score recompute
  42. 2026-08-30 01:22 UTCEPSS rescore
  43. 2026-08-29 03:46 UTCEG score recompute
  44. 2026-08-28 21:41 UTCEPSS rescore
  45. 2026-08-27 19:21 UTCEG score recompute
  46. 2026-08-27 14:25 UTCEPSS rescore
  47. 2026-08-26 21:10 UTCEG score recompute
  48. 2026-08-26 14:46 UTCEPSS rescore
  49. 2026-08-25 23:14 UTCEG score recompute
  50. 2026-08-25 13:48 UTCEPSS rescore
  51. 2026-08-24 14:42 UTCEG score recompute
  52. 2026-08-23 06:10 UTCEG score recompute
  53. 2026-08-23 00:19 UTCEPSS rescore
  54. 2026-08-22 08:28 UTCEG score recompute
  55. 2026-08-21 23:49 UTCEPSS rescore
  56. 2026-08-20 23:55 UTCEG score recompute
  57. 2026-08-20 22:55 UTCEPSS rescore
  58. 2026-08-20 02:10 UTCEG score recompute
  59. 2026-08-19 17:03 UTCEPSS rescore
  60. 2026-08-19 04:19 UTCEG score recompute
  61. 2026-08-19 04:11 UTCEG score recompute
  62. 2026-08-18 20:22 UTCEG score recompute
  63. 2026-08-18 19:19 UTCEG score recompute
  64. 2026-08-18 18:44 UTCEG score recompute
  65. 2026-08-18 18:43 UTCMITRE cvelistV5first tracked

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 PoCmasasron/CopyEscape-CVE-2026-17106
    First seen Aug 9, 2026

    PoC repository for the blog post CopyEscape: Taking Over Docker Hosts with docker cp

    Open source ↗

Frequently asked(5)

What is CVE-2026-17106?
CVE-2026-17106 is a high vulnerability published on August 18, 2026. The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the ApplyLayer helpers) do not confine filesystem operations to the destination directory. The extractor decides where each archive entry lands using lexical string checks and then performs the…
When was CVE-2026-17106 disclosed?
CVE-2026-17106 was first published in the National Vulnerability Database on August 18, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17106 actively exploited?
CVE-2026-17106 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.2% of all scored CVEs.
What is the CVSS score of CVE-2026-17106?
CVE-2026-17106 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-17106?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17106, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-17106

Explore →

Is Your Infrastructure Affected by CVE-2026-17106?

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

Start Free Scan →Browse All CVEs