CVE Intelligence
Skip to main content
HIGHpublic exploit

CVE-2026-34040

Moby: AuthZ plugin bypass with oversized request body

Moby is an open source container framework. Prior to version 29.3.1, a security vulnerability has been detected that allows attackers to bypass authorization plugins (AuthZ). This issue has been patched in version 29.3.1.

Published Updated Sources: cvelistV5, GitHub_M

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

10%

chance of exploitation in 30 days

Affects

moby

moby

CVSS base

8.8

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

moby

Products (1)

moby

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.8CVSS 3.1HIGH——cvelistV5

Weakness & attack patterns

  • CWE-288

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1083File and Directory Discovery
  • T1211Exploitation for Defensive Evasion
  • T1542.002Pre-OS Boot: Component Firmware

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Indexed by

poc in github

References

2 on the record

Elsewhere on this site

  • mobyevery CVE for this vendor
  • CWE-288other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.