1sealsemantic last-mile verification

Research / Finding

AuthZ plugin bypass with oversized request body

F-MOBY-001-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Read the evidence · View in research browse

Recorded evidence

8.8high
CVE-2026-34040CVEmoby/moby

AuthZ plugin bypass with oversized request body

Upstream fixed versions: Docker Engine: 29.3.1

patched
details
Finding IDs
F-MOBY-001-001
CVE
CVE-2026-34040
GHSA
GHSA-x744-4wpc-v9h2
Status
patched
Fixed in
Docker Engine: 29.3.1
Recorded credit
1seal / Oleh Konko (@1seal)
Note
GHSA-x744-4wpc-v9h2
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CVE registry state
PUBLISHED
CVE state checked
Upstream title
AuthZ plugin bypass with oversized request body
Upstream publication
Upstream updated
Metadata fetched
Upstream fixed versions
Docker Engine: 29.3.1
Upstream affected ranges
Docker Engine: < 29.3.1
Upstream @1seal credit
@1seal: reporter (accepted)

F-MOBY-001-001: Access control. An oversized request body bypasses the authorization plugin decision. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-MOBY-001-001

Security area (1seal assessment): Authorization. An oversized request body bypasses the authorization plugin decision. Reviewed 24 Sep 2026.

—score not recorded
moby/mobyReported fixmoby/moby

pkg/authz: Reject requests exceeding body size limit

fixed publicly
details
Finding IDs
F-MOBY-001-001
Status
fixed publicly
Reported via
security contact
Note
public fix commit 7a767b27fd12 appears to address the reported issue. GHSA-x744-4wpc-v9h2 / CVE-2026-34040 published with credit to 1seal / Oleh Konko.

F-MOBY-001-001: Access control. An oversized request body bypasses the authorization plugin decision. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-MOBY-001-001

Security area (1seal assessment): Authorization. An oversized request body bypasses the authorization plugin decision. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.