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.4% (36th percentile of EPSS-scored CVEs). 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 — Patch released 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.4%CVSS: 7.1Exploit: Elevated riskExposed services: Not assessed

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.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100CISA SSVC

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%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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(11)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17906390092026-09-29redhat
redhatrhacm2/acm-grafana-rhel9:17902406932026-09-28redhat
redhatpodman-6:5.8.2-7.el9_82026-09-22redhat
redhatubi10/podman:7:5.8.2-9.el10_22026-09-22redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17884419832026-09-17redhat
redhatrhem/flightctl-worker-rhel10:17894867402026-09-16redhat
redhatrhem/flightctl-worker-rhel9:17894880612026-09-16redhat
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 rangeFix by version rangeDependents
golang-github-moby-go-archive0.2.0-1
  • every version up to 0.3.3-1: fixed in 0.3.3-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/moby/go-archive—
  • every version up to 0.3.0: fixed in 0.3.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 100× 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.

Showing the most recent 100 of 140 total refreshes for this CVE.

  1. 2026-10-05 06:05 UTCEG score recompute
  2. 2026-10-05 06:05 UTCVendor advisory
  3. 2026-10-04 23:21 UTCEPSS rescore
  4. 2026-10-04 16:16 UTCVendor advisory
  5. 2026-10-04 05:18 UTCVendor advisory
  6. 2026-10-03 17:37 UTCEG score recompute
  7. 2026-10-03 17:37 UTCVendor advisory
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 01:57 UTCEG score recompute
  10. 2026-10-03 01:57 UTCVendor advisory
  11. 2026-10-02 15:06 UTCVendor advisory
  12. 2026-10-02 01:26 UTCEG score recompute
  13. 2026-10-02 01:26 UTCVendor advisory
  14. 2026-10-01 19:49 UTCEPSS rescore
  15. 2026-10-01 07:40 UTCVendor advisory
  16. 2026-09-30 20:49 UTCEG score recompute
  17. 2026-09-30 20:49 UTCVendor advisory
  18. 2026-09-30 15:02 UTCEPSS rescore
  19. 2026-09-30 09:47 UTCEG score recompute
  20. 2026-09-30 09:47 UTCVendor advisory
  21. 2026-09-29 15:20 UTCEPSS rescore
  22. 2026-09-28 21:55 UTCEG score recompute
  23. 2026-09-28 21:55 UTCVendor advisory
  24. 2026-09-28 13:51 UTCEPSS rescore
  25. 2026-09-28 05:41 UTCVendor advisory
Show 75 more
  1. 2026-09-27 18:50 UTCEG score recompute
  2. 2026-09-27 18:50 UTCVendor advisory
  3. 2026-09-27 13:47 UTCEPSS rescore
  4. 2026-09-27 07:55 UTCEG score recompute
  5. 2026-09-27 07:55 UTCVendor advisory
  6. 2026-09-26 15:58 UTCEPSS rescore
  7. 2026-09-25 12:22 UTCVendor advisory
  8. 2026-09-25 01:25 UTCEG score recompute
  9. 2026-09-25 01:25 UTCVendor advisory
  10. 2026-09-24 07:11 UTCVendor advisory
  11. 2026-09-23 20:19 UTCEG score recompute
  12. 2026-09-23 20:19 UTCVendor advisory
  13. 2026-09-23 07:15 UTCVendor advisory
  14. 2026-09-22 20:24 UTCEG score recompute
  15. 2026-09-22 20:24 UTCVendor advisory
  16. 2026-09-22 06:17 UTCEG score recompute
  17. 2026-09-22 06:17 UTCVendor advisory
  18. 2026-09-21 19:04 UTCVendor advisory
  19. 2026-09-21 08:11 UTCVendor advisory
  20. 2026-09-20 20:29 UTCEG score recompute
  21. 2026-09-20 20:29 UTCVendor advisory
  22. 2026-09-20 09:38 UTCVendor advisory
  23. 2026-09-19 21:44 UTCEG score recompute
  24. 2026-09-19 21:44 UTCVendor advisory
  25. 2026-09-19 10:54 UTCVendor advisory
  26. 2026-09-18 23:32 UTCEG score recompute
  27. 2026-09-18 23:32 UTCVendor advisory
  28. 2026-09-18 19:27 UTCEPSS rescore
  29. 2026-09-18 12:41 UTCVendor advisory
  30. 2026-09-18 01:42 UTCEG score recompute
  31. 2026-09-18 01:42 UTCVendor advisory
  32. 2026-09-17 14:51 UTCVendor advisory
  33. 2026-09-17 03:43 UTCVendor advisory
  34. 2026-09-16 15:58 UTCEG score recompute
  35. 2026-09-16 15:58 UTCVendor advisory
  36. 2026-09-16 14:07 UTCEPSS rescore
  37. 2026-09-16 05:14 UTCEPSS rescore
  38. 2026-09-16 04:51 UTCVendor advisory
  39. 2026-09-15 17:27 UTCVendor advisory
  40. 2026-09-15 06:34 UTCEG score recompute
  41. 2026-09-15 06:34 UTCVendor advisory
  42. 2026-09-14 19:43 UTCVendor advisory
  43. 2026-09-14 06:54 UTCVendor advisory
  44. 2026-09-13 20:03 UTCEG score recompute
  45. 2026-09-13 20:03 UTCVendor advisory
  46. 2026-09-13 16:46 UTCEPSS rescore
  47. 2026-09-13 09:11 UTCVendor advisory
  48. 2026-09-12 22:21 UTCEG score recompute
  49. 2026-09-12 22:21 UTCVendor advisory
  50. 2026-09-12 15:00 UTCEPSS rescore
  51. 2026-09-12 11:30 UTCVendor advisory
  52. 2026-09-12 00:04 UTCEG score recompute
  53. 2026-09-12 00:04 UTCVendor advisory
  54. 2026-09-11 14:52 UTCEPSS rescore
  55. 2026-09-11 13:13 UTCEG score recompute
  56. 2026-09-11 13:13 UTCVendor advisory
  57. 2026-09-11 09:36 UTCEPSS rescore
  58. 2026-09-11 00:38 UTCVendor advisory
  59. 2026-09-10 12:53 UTCEG score recompute
  60. 2026-09-10 12:53 UTCVendor advisory
  61. 2026-09-10 09:34 UTCEPSS rescore
  62. 2026-09-10 02:03 UTCVendor advisory
  63. 2026-09-09 15:12 UTCVendor advisory
  64. 2026-09-09 03:24 UTCEG score recompute
  65. 2026-09-09 03:24 UTCVendor advisory
  66. 2026-09-08 22:00 UTCEPSS rescore
  67. 2026-09-08 02:59 UTCVendor advisory
  68. 2026-09-07 16:08 UTCVendor advisory
  69. 2026-09-07 01:16 UTCVendor advisory
  70. 2026-09-06 14:26 UTCEG score recompute
  71. 2026-09-06 14:26 UTCVendor advisory
  72. 2026-09-06 13:47 UTCEPSS rescore
  73. 2026-09-06 03:35 UTCVendor advisory
  74. 2026-09-05 16:44 UTCEG score recompute
  75. 2026-09-05 16:44 UTCVendor advisory

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 ↗

Related CVEs(same vendor + same CWE)

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 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.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17106?
CVE-2026-17106 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-17106?
A fix for CVE-2026-17106 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17106 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs