CVE-2026-41567

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th 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
Trending — 3 sources updated this week

Also known asEUVD-2026-34779 (ENISA EUVD) · GHSA-x86f-5xw2-fm2r (GitHub Security Advisories)Source: ENISA EUVD

7.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Moby is an open source container framework. In versions prior to 29.5.1 and in moby/moby v2 prior to v2.0.0-beta.14, when a compressed archive is uploaded to a container via PUT /containers/{id}/archive or piped through docker cp -, the daemon resolves decompression binaries (such as xz or unpigz) from the container's filesystem rather than the host's due to incorrect ordering of operations. A malicious container image containing a trojanized decompression binary can achieve arbitrary code execution with full daemon privileges, including host root UID and unrestricted capabilities, when a user uploads a compressed (xz or gzip) archive into that container. This issue is fixed in Docker Engine 29.5.1 and moby/moby v2.0.0-beta.14. Workarounds include only running containers from trusted images, using authorization plugins to restrict access to the PUT /containers/{id}/archive endpoint, and avoiding piping compressed archives into containers created from untrusted images

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity72% × 45%
Impact severity (EG Severity): CVSS 7.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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.
EPSS PROB
0.2%
EPSS %ILE
4th
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.2): severity, escalated by confirmed exploitation. This CVE's 7.2 is its impact severity (EG Severity), not escalated.

EG Severity
7.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 or medium mission impact; Track* at high (mission-essential systems).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: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (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.

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

May 18, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Jun 11, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

`PUT /containers/{id}/archive` executes container binary on the host · Advisory · moby/moby · GitHub

https://github.com/moby/moby/security/advisories/GHSA-x86f-5xw2-fm2r

Vendor Advisories for CVE-2026-41567(6)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatsource-to-image/source-to-image-rhel9:17847280362026-08-06redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845613762026-07-23redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845620602026-07-21redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17840606812026-07-16redhat
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat

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

(7 across 5 ecosystems)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/docker/docker—
  • every version through 28.5.2: no fix on record
  • every version on: no fix on record
—
github.com/moby/moby—
  • every version through 28.5.2: no fix on record
  • every version on: no fix on record
—
github.com/moby/moby/v2—
  • every version up to 2.0.0-beta.14: fixed in 2.0.0-beta.14
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io20.10.10+dfsg1-1 ... 28.5.2+dfsg4-3 (61 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io20.10.24+dfsg1-1 ... 28.5.2+dfsg4-5 (47 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io26.1.5+dfsg1-9
  • every version up to 26.1.5+dfsg1-9+deb13u1: fixed in 26.1.5+dfsg1-9+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io26.1.5+dfsg1-10 ... 28.5.2+dfsg4-2 (19 versions)
  • every version up to 28.5.2+dfsg4-3: fixed in 28.5.2+dfsg4-3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 245 refreshes 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 145 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41567?
CVE-2026-41567 is a high-severity vulnerability; its CVE record was published on May 18, 2026. Moby is an open source container framework. In versions prior to 29.5.1 and in moby/moby v2 prior to v2.0.0-beta.14, when a compressed archive is uploaded to a container via PUT /containers/{id}/archive or piped through docker cp -, the daemon resolves decompression binaries (such as xz or unpigz)…
When was the CVE record for CVE-2026-41567 published?
The CVE record for CVE-2026-41567 was published on May 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-41567 actively exploited?
CVE-2026-41567 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41567?
CVE-2026-41567 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-41567?
A fix for CVE-2026-41567 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41567 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-41567

Explore →

Is Your Infrastructure Affected by CVE-2026-41567?

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

Book a Demo →Browse All CVEs