CVE-2026-42561: Semgrep · python-multipart has Denial of Service via unbounded multipart part headers
Affects semgrepSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 1.165.0 soon.
Data as of 19 Nov 2026, 19:38 UTC
- Patch
- Available – fixed in 1.165.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 May 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.165.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.165.0 or later to apply the official fix. If immediate upgrade is not possible, mitigate exposure by enforcing request body size limits at the server, proxy, or framework level. Note that this is only a partial mitigation, as affected versions still parse multipart headers without limits on header count and size.
Description
python-multipart versions from 1.137.0 up to but not including 1.165.0 contain a denial of service vulnerability in multipart part header parsing. The vulnerability allows an attacker to cause excessive CPU consumption by sending multipart/form-data requests with either many repeated headers without termination or a single very large header value. This can lead to worker or event-loop delays in ASGI applications using frameworks like Starlette or FastAPI. The issue is fixed in version 1.165.0.