CVE-2026-17106

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-61112 (ENISA EUVD) · GHSA-hfg8-hc9c-6c3h (GitHub Security Advisories) · GO-2026-6253 (OSV.dev)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: Public PoCExposed 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
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-08). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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
Web page

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
Web page

Docker Desktop release notes | Docker Docs

https://docs.docker.com/desktop/release-notes/#4860
GitHub advisoryMentions a patch (unverified)

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

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17927211922026-10-29redhat
redhatdevspaces/traefik-rhel9:17924641772026-10-26redhat
redhatrhoai/odh-model-registry-rhel9:17918693652026-10-19redhat
redhatquay/quay-rhel8:17913145142026-10-08redhat
redhatquay/quay-rhel8:17908084432026-10-07redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17906390092026-09-29redhat
redhatrhacm2/acm-grafana-rhel9:17902406932026-09-28redhat
redhatubi10/podman:7:5.8.2-9.el10_22026-09-22redhat
redhatpodman-6:5.8.2-7.el9_82026-09-22redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17884419832026-09-17redhat
redhatrhem/flightctl-worker-rhel9:17894880612026-09-16redhat
redhatrhem/flightctl-worker-rhel10:17894867402026-09-16redhat
redhatopenshift-logging/cluster-logging-rhel9-operator:17884395052026-09-10redhat
redhatpodman-main-6.0.2-2.2.hum12026-08-10redhat
gogithub.com/moby/go-archive @ 0.3.0 (fixes < 0.3.0)—ghsa

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

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 204 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCmasasron/CopyEscape-CVE-2026-17106
    Published 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-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-17106 published?
The CVE record for CVE-2026-17106 was published on August 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
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 (38th 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.