Docker Engine
CVE-2026-34040
HIGH
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Docker API is typically local (AV:L), low-priv API client suffices (PR:L), crafted request is trivial (AC:L), and AuthZ bypass yields full container/host control (C:H/I:H/A:H).
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
8DescriptionNVD
Summary
A security vulnerability has been detected that allows attackers to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low.
This is an incomplete fix for CVE-2024-41110.
Impact
If you don't use AuthZ plugins, you are not affected.
Using a specially-crafted API request, an attacker could make the Docker daemon forward the request to an authorization plugin without the body. The authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.
Anyone who depends on authorization plugins that introspect the request body to make access control decisions is potentially impacted.
Workarounds
If unable to update immediately:
- Avoid using AuthZ plugins that rely on request body inspection for security decisions.
- Restrict access to the Docker API to trusted parties, following the principle of least privilege.
Credits
- 1seal / Oleh Konko (@1seal)
- Cody (c@wormhole.guru)
- Asim Viladi Oglu Manizada (@manizada)
Resources
AnalysisAI
Authorization bypass in Docker Engine (moby) allows API clients to evade AuthZ plugin policy decisions by issuing requests whose body is not forwarded to the plugin, causing it to approve operations it would otherwise deny. This is an incomplete-fix regression of CVE-2024-41110 affecting deployments that rely on AuthZ plugins inspecting request bodies; publicly available exploit code exists but EPSS is 0.01% and SSVC exploitation status is 'none'.
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires (1) Docker Engine deployed with an authorization plugin enabled via --authorization-plugin that makes policy decisions based on inspecting the HTTP request body (e.g., container create payloads, bind-mount specifications, capability lists) - hosts without an AuthZ plugin are explicitly not affected per the vendor; (2) the attacker must already be able to reach the Engine API (local unix socket, TCP endpoint, or a delegated client cert) at PR:L privilege per the CVSS vector; (3) the attacker must be able to issue an HTTP API request that triggers the body-stripping path (zero-length / specific Content-Length manipulation against the legacy drainBody logic). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals diverge sharply: CVSS 7.8 (High) with C:H/I:H/A:H and SSVC Technical Impact 'total' indicate severe consequences when exploitable, but exploitation is gated on the operator actually running an AuthZ plugin that uses body introspection - a deliberately enabled, non-default configuration. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A low-privileged Docker API client on a host protected by an AuthZ plugin sends a crafted API call (for example POST /containers/create with a privileged/host-mount payload) using Content-Length: 0 or otherwise inducing the daemon to forward the request to the plugin without the body. The plugin, seeing only the URL and headers, approves the call, but dockerd then executes the real request body and creates the privileged container, granting the attacker root on the host. … |
| Remediation | Vendor-released patch: upgrade Docker Engine to docker-v29.3.1 or later (https://github.com/moby/moby/releases/tag/docker-v29.3.1); SUSE users can apply SUSE-SU-2026:1205 (https://www.suse.com/support/update/SUSE-SU-2026:1205/). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all Docker Engine deployments using AuthZ plugins and assess exposure scope. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More from same product – last 7 days
Unauthenticated remote attackers can invoke MCP tool handlers and exfiltrate the operator's long-lived Meta Graph API ac
Unauthenticated remote code execution in Crawl4AI versions <= 0.8.6 allows attackers to escape the AST-based sandbox in
Privileged GitHub Actions workflow injection in Quest Bot (Discord moderation bot) prior to version 1.0.3 allows remote
Production deployment compromise in Duck Site before 1.0.1 allows remote attackers to push attacker-controlled code as t
Server-side request forgery in Crawl4AI's Docker API server (versions <= 0.8.8) allows unauthenticated remote attackers
Vendor StatusVendor
SUSE
Severity: HighShare
External POC / Exploit Code
Leaving vuln.today
GHSA-x744-4wpc-v9h2