CVE-2026-42561: Python-Multipart: Denial of Service via unbounded multipart part headers
Summary
python-multipart has a denial of service vulnerability in multipart part header parsing. When parsing multipart/form-data, MultipartParser previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion.
Impact
Applications that parse attacker-controlled multipart/form-data with affected versions of python-multipart can experience CPU exhaustion. ASGI applications using Starlette, FastAPI, or other frameworks that invoke python-multipart may have worker or event-loop delays while processing malicious upload requests.
Details
The affected parser states are HEADERFIELDSTART, HEADERFIELD, HEADERVALUESTART, HEADERVALUE, and HEADERVALUEALMOSTDONE. The issue can be triggered by:
- A multipart part with an oversized individual header value. - A multipart part with many repeated header lines or an unterminated header block.
Both variants are addressed by enforcing default parser limits for maximum header count and maximum header size.
Mitigation
Upgrade to python-multipart 0.0.27 or later.
If upgrading is not immediately possible, reduce exposure by enforcing request body size limits at the server, proxy, or framework layer. This is only a mitigation; affected versions of python-multipart still parse multipart part headers without the default header count and header size limits.
Other sources
Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.27, python-multipart has a denial of service vulnerability in multipart part header parsing. When parsing multipart/form-data, MultipartParser previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion. This vulnerability is fixed in 0.0.27.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/python-multipartto a version that resolves this vulnerability.Fixed in 0.0.27 - Upgrade
Upgrade
python-multipartto a version that resolves this vulnerability.Fixed in 0.0.27 - Compensating control
If upgrading is not immediately possible, reduce exposure by enforcing request body size limits at the server, proxy, or framework layer for multipart/form-data requests.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-42561?
CVE-2026-42561 is classified as a denial of service vulnerability.
How do I fix CVE-2026-42561?
To fix CVE-2026-42561, upgrade `python-multipart` to version 0.0.27 or later.
What does CVE-2026-42561 affect?
CVE-2026-42561 affects the `python-multipart` package when handling multipart/form-data requests.
What is the main issue with CVE-2026-42561?
The main issue with CVE-2026-42561 is the lack of limits on the number and size of part headers in multipart parsing.
What type of attack is possible with CVE-2026-42561?
An attacker could exploit CVE-2026-42561 to send crafted requests that could lead to a denial of service.