CVE-2026-53540: python-multipart · Negative Content-Length in parse_form buffers the entire body in memory
Affects semgrepSource GCVE Database
Not known to be exploited · CVSS 3.7 Low : upgrade to 1.166.0 when convenient.
Data as of 19 Nov 2026, 19:38 UTC
- Patch
- Available – fixed in 1.166.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 22 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade semgrep to 1.166.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewsemgreppkg:brew/semgrepOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade python-multipart to version 1.166.0 or later, which rejects negative Content-Length headers with a ValueError before reading the request body. This prevents unbounded memory buffering. If upgrading is not immediately possible, ensure that any code calling parse_form() normalizes or validates the Content-Length header to reject negative values before passing it to the function.
Description
The python-multipart library's parse_form() function did not validate the Content-Length header for negative values, causing it to read the entire request body into memory at once instead of in chunks. This behavior only occurs if parse_form() is called directly with an attacker-controlled negative Content-Length header, which is uncommon in typical frameworks. The issue can degrade availability by increasing memory usage under concurrent requests but does not cause complete denial of service or data compromise. The vulnerability is fixed in version 1.166.0 and later.