CVE-2026-41567

HIGHPre-NVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% 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 week
7.2EG
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.2Exploit: None knownExposed: 0

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.2(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity72% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 18, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Jun 11, 2026
Patch available. Sources: github.
github Patch Available

`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 / EcosystemFixed in / 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 rangeFixed inDependents
github.com/docker/docker———
github.com/moby/moby———
github.com/moby/moby/v2—2.0.0-beta.14—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
docker.io20.10.10+dfsg1-1 ... 28.5.2+dfsg4-3 (61 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
docker.io20.10.24+dfsg1-1 ... 28.5.2+dfsg4-4 (46 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
docker.io26.1.5+dfsg1-926.1.5+dfsg1-9+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
docker.io26.1.5+dfsg1-10 ... 28.5.2+dfsg4-2 (19 versions)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 / 57× 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 198 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-41567?
CVE-2026-41567 is a high vulnerability 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 CVE-2026-41567 disclosed?
CVE-2026-41567 was first published in the National Vulnerability Database on May 18, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41567 actively exploited?
CVE-2026-41567 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 94.4% of all scored CVEs.
What is the CVSS score of CVE-2026-41567?
CVE-2026-41567 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-41567?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41567, 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-41567

Explore →

Is Your Infrastructure Affected by CVE-2026-41567?

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

Start Free Scan →Browse All CVEs