CVE-2026-53538
published 2026-06-22CVE-2026-53538: Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.30, QuerystringParser treated ; as a field separator in…
PriorityP415low3.7CVSS 3.1
AVNACHPRNUINSUCNILAN
EPSS
0.18%
7.3th percentile
Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.30, QuerystringParser treated ; as a field separator in application/x-www-form-urlencoded bodies, in addition to &. The WHATWG URL standard, modern browsers, and Python's urllib.parse (since the CVE-2021-23336 fix) treat only & as a separator. This creates a parser differential: the same bytes are tokenized into different fields than a WHATWG compliant intermediary would produce, allowing an attacker to smuggle extra form fields past an upstream body inspecting component. This vulnerability is fixed in 0.0.30.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| fastapiexpert | python-multipart | < 0.0.30 | 0.0.30 |
| kludex | python-multipart | >= 0 < 0.0.30 | 0.0.30 |
CVSS provenance
nvdv3.13.7LOWCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
ghsa5.9MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Kludex python-multipart up to 0.0.29 on Python interpretation conflict (GHSA-6jv3-5f52-599m)
vuldb·2026-06-22·CVSS 3.7
CVE-2026-53538 [LOW] Kludex python-multipart up to 0.0.29 on Python interpretation conflict (GHSA-6jv3-5f52-599m)
A vulnerability categorized as problematic has been discovered in Kludex python-multipart up to 0.0.29 on Python. This impacts an unknown function. The manipulation results in interpretation conflict.
This vulnerability is cataloged as CVE-2026-53538. The attack may be launched remotely. There is no exploit available.
It is advisable to upgrade the affected component.
GHSA
python-multipart: Semicolon treated as querystring field separator enables parameter smuggling
ghsa·2026-06-15·CVSS 5.9
CVE-2026-53538 [MEDIUM] CWE-436 python-multipart: Semicolon treated as querystring field separator enables parameter smuggling
python-multipart: Semicolon treated as querystring field separator enables parameter smuggling
### Summary
`QuerystringParser` treated `;` as a field separator in `application/x-www-form-urlencoded` bodies, in addition to `&`. The [WHATWG URL standard](https://url.spec.whatwg.org/#urlencoded-parsing), modern browsers, and Python's `urllib.parse` (since the CVE-2021-23336 fix) treat only `&` as a separator. This creates a parser differential: the same bytes are tokenized into different fields than a WHATWG compliant intermediary would produce, allowing an attacker to smuggle extra form fields past an upstream body inspecting component.
### Details
In `python_multipart/multipart.py`, the `FIELD_NAME` and `FIELD_DATA` states located the next separator by scanning for `&` and, failing that
No detection rules found.
No public exploits indexed.
2026-06-22
Published