CVE-2026-53540

Python-Multipart: Negative Content-Length in parse_form buffers the entire body in memory

LOW
3.7
CVSS Score
Published: June 22, 2026 at 04:58 PM UTC
Updated: October 25, 2026 at 11:10 PM UTC
2 products affected across 2 vendorsPython MultipartPython Multipart

Using python-multipart by Kludex?

Get instant alerts when new vulnerabilities affect python-multipart - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW3.7
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.31, parse_form() did not validate the Content-Length header before using it to bound its chunked read of the request body. A negative Content-Length turned the bounded read into a read-until-EOF, so the entire body was loaded into memory in a single read instead of in fixed-size chunks. This vulnerability is fixed in 0.0.31.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.0.31
Affected range stops below 0.0.31, so it looks safe — our inference, not a vendor statement
v < 0.0.31
Affected range stops below 0.0.31, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

3.7LOWGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-1284

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card