Docker’s 1MB authz bypass: are your container controls enough?

TL;DR: A one-megabyte size check in Docker Engine silently drops oversized request bodies before AuthZ plugins can inspect them, enabling a single HTTP request to create privileged containers with host access, according to Cyera. The failure shows that middleware which truncates input without failing closed turns authorization into a blind spot, not a control.

Editorial analysis by NHI Mgmt Group, based on content published by Cyera: “One Megabyte to Root: How a Size Check Broke Docker’s Last Line of Defense”.

By the numbers:

• Docker has 92% adoption among IT professionals.
• Docker processes over 20 billion container image pulls per month.
• Docker Engine 29.3.1 contains the patch for CVE-2026-34040.

Key questions

Q: What breaks when Docker AuthZ plugins do not see the full request body?

A: The authorization decision breaks because the plugin evaluates incomplete evidence while the daemon still executes the full container request.

Q: Why do oversized API requests create container security risk even when AuthZ plugins are installed?

A: Because the plugin only protects what it can inspect.

Q: How should teams test whether Docker admission controls are actually working?

A: Test with the same kinds of inputs attackers use to break assumptions: oversized bodies, chunked transfer encoding, and requests that push policy-relevant fields past middleware limits.

Practitioner guidance

• Audit container admission for silent truncation Verify that every Docker API path and related admission proxy rejects oversized request bodies instead of forwarding them with hidden content removed.
• Test policy engines with boundary-crossing payloads Send oversized and chunked requests to the same endpoints your AuthZ plugins inspect, then confirm that the request is denied before the daemon can act.
• Review host filesystem exposure from privileged containers Inventory which host paths, credentials, and runtime tokens become reachable if a privileged container is created through an admission failure.

Bottom line: The core problem is not container escape alone but authorization that can be bypassed before a container is even created.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →