CVE-2024-41110

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 2.9%, top 13% 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, nvd
Elevated
9.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 16%CVSS: 9.9Exploit: NoneExposed: 0

A fix is available — apply it.

Moby is an open-source project created by Docker for software containerization. A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low.

Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an authorization plugin without the body. In certain circumstances, the authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.

A security issue was discovered In 2018, where an attacker could bypass AuthZ plugins using a specially crafted API request. This could lead to unauthorized actions, including privilege escalation. Although this issue was fixed in Docker Engine v18.09.1 in January 2019, the fix was not carried forward to later major versions, resulting in a regression. Anyone who depends on authorization plugins that introspect the request and/or response body to make access control decisions is potentially impacted.

Docker EE v19.03.x and all versions of Mirantis Container Runtime are not vulnerable.

docker-ce v27.1.1 containes patches to fix the vulnerability. Patches have also been merged into the master, 19.03, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches. If one is unable to upgrade immediately, avoid using AuthZ plugins and/or restrict access to the Docker API to trusted parties, following the principle of least privilege.

CVSS v3
9.9
EG Score
9.9(medium)
EPSS
96.6%
KEV
Not listed

Published

July 24, 2024

Last Modified

April 15, 2026

Advisory Details (10)

Auto-updated Jul 5, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit fc274cd2ff4c (moby/moby)

Fix landed in moby/moby commit fc274cd2ff4c — awaiting tagged release

https://github.com/moby/moby/commit/fc274cd2ff4cf3b48c91697fb327dd1fb95588fb
github_commit

commit cc13f9525111 (moby/moby)

Fix landed in moby/moby commit cc13f9525111 — awaiting tagged release

https://github.com/moby/moby/commit/cc13f952511154a2866bddbb7dddebfe9e83b801
github_commit

commit ae2b3666c517 (moby/moby)

Fix landed in moby/moby commit ae2b3666c517 — awaiting tagged release

https://github.com/moby/moby/commit/ae2b3666c517c96cbc2adf1af5591a6b00d4ec0f
github_commit

commit ae160b4edddb (moby/moby)

Fix landed in moby/moby commit ae160b4edddb — awaiting tagged release

https://github.com/moby/moby/commit/ae160b4edddb72ef4bd71f66b975a1a1cc434f00
github_commit

commit a79fabbfe841 (moby/moby)

Fix landed in moby/moby commit a79fabbfe841 — awaiting tagged release

https://github.com/moby/moby/commit/a79fabbfe84117696a19671f4aa88b82d0f64fc1
github_commit

commit a31260625655 (moby/moby)

Fix landed in moby/moby commit a31260625655 — awaiting tagged release

https://github.com/moby/moby/commit/a31260625655cff9ae226b51757915e275e304b0
github_commit

commit 852759a7df45 (moby/moby)

Fix landed in moby/moby commit 852759a7df45 — awaiting tagged release

https://github.com/moby/moby/commit/852759a7df454cbf88db4e954c919becd48faa9b
github_commit

commit 65cc597cea28 (moby/moby)

Fix landed in moby/moby commit 65cc597cea28 — awaiting tagged release

https://github.com/moby/moby/commit/65cc597cea28cdc25bea3b8a86384b4251872919
github_commit

commit 42f40b1d6dd7 (moby/moby)

Fix landed in moby/moby commit 42f40b1d6dd7 — awaiting tagged release

https://github.com/moby/moby/commit/42f40b1d6dd7562342f832b9cd2adf9e668eeb76
github_commit

commit 411e817ddf71 (moby/moby)

Fix landed in moby/moby commit 411e817ddf71 — awaiting tagged release

https://github.com/moby/moby/commit/411e817ddf710ff8e08fa193da80cb78af708191

Vendor Advisories for CVE-2024-41110(2)

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

Patch Availability(4)

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 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/docker/docker27.1.1+incompatible
github.com/moby/moby27.1.1+incompatible

Weakness Classification(3)

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

Additional Vendor Advisories

(3)

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 7× in last 7d / 39× 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 109 total refreshes for this CVE.

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

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 PoCvvpoglazov/cve-2024-41110-checker
    First seen Jul 25, 2024
    Open source ↗

Frequently asked(5)

What is CVE-2024-41110?
CVE-2024-41110 is a critical vulnerability published on July 24, 2024. Moby is an open-source project created by Docker for software containerization. A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being…
When was CVE-2024-41110 disclosed?
CVE-2024-41110 was first published in the National Vulnerability Database on July 24, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-41110 actively exploited?
CVE-2024-41110 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-41110?
CVE-2024-41110 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2024-41110?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-41110, 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-2024-41110

Explore →

Is Your Infrastructure Affected by CVE-2024-41110?

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