CVE-2024-41110
A public proof of concept exists; no exploitation attested.
- Published2024-07-24
- WeaknessCWE-187 · CWE-444 · CWE-863
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2024-07-2417:15CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-41110?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-41110?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
CISA-ADP| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 19.x | ≥ 19.0.0, ≤ 19.03.15 | no fix published | CISA-ADP |
| 20.x | ≥ 20.0.0, ≤ 20.10.27 | no fix published | CISA-ADP |
| 23.0 | ≥ 23.0.0, ≤ 23.0.14 | no fix published | CISA-ADP |
| 24.0 | ≥ 24.0.0, ≤ 24.0.9 | no fix published | CISA-ADP |
| 25.0 | ≥ 25.0.0, ≤ 25.0.5 | no fix published | CISA-ADP |
| 26.0 | ≥ 26.0.0, ≤ 26.0.2 | no fix published | CISA-ADP |
| 26.1 | ≥ 26.1.0, ≤ 26.1.14 | no fix published | CISA-ADP |
| 27.1 | = 27.1.0 | no fix published | CISA-ADP |
| 27.0 | ≥ 27.0.0, ≤ 27.0.3 | no fix published | CISA-ADP |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
No fix published by the sources we read yet. NVD record
Detection
read 2026-10-23 19:24 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 2 repositories, unverifiedvvpoglazov/cve-2024-41110-checkerPauloParoPP/CVE-2024-41110-SCAN PoC-in-GitHub
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2024-07-26
- OpenCVESSVC decisionnone—
- CNACVSS 3.19.9read 2026-10-23
- CNAweakness (CWE)CWE-187, CWE-444, CWE-863read 2026-10-23
- FIRST EPSSEPSS score16.5 %read 2026-10-23
- PoC-in-GitHubproof of concept2read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Published
- 2024-07-24
- Last Modified
- 2026-06-17
- NVD status
- Deferred
Frequently asked questions
What is CVE-2024-41110?
Is CVE-2024-41110 actively exploited?
What is the CVSS score for CVE-2024-41110?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.