CVE-2026-53538: CWE-436: Interpretation Conflict in Kludex python-multipart
A vulnerability in python-multipart prior to version 0.0.30 allows interpretation conflicts in parsing application/x-www-form-urlencoded bodies. The QuerystringParser treated the semicolon (;) as a field separator in addition to the ampersand (&), which is inconsistent with the WHATWG URL standard and modern browsers. This discrepancy can enable an attacker to smuggle extra form fields past upstream body inspection components. The issue is fixed in version 0.0.30.
AI Analysis
Technical Summary
The python-multipart library, used for streaming multipart parsing in Python, had a parsing inconsistency before version 0.0.30. Specifically, its QuerystringParser treated the semicolon character as a separator in application/x-www-form-urlencoded bodies, whereas the WHATWG URL standard and modern browsers treat only the ampersand as a separator. This mismatch creates a parser differential, allowing attackers to inject additional form fields that may bypass upstream inspection mechanisms. This vulnerability is identified as CWE-436 (Interpretation Conflict) and CWE-444 (Inconsistent Interpretation of HTTP Requests). The vulnerability is resolved in python-multipart version 0.0.30.
Potential Impact
This vulnerability allows an attacker to smuggle extra form fields past upstream body inspection components due to inconsistent parsing of field separators. While it does not directly compromise confidentiality or availability, it can lead to integrity issues by enabling injection of unexpected form fields, potentially affecting application logic or security controls relying on accurate request parsing.
Mitigation Recommendations
Upgrade python-multipart to version 0.0.30 or later, where the QuerystringParser no longer treats semicolon as a field separator, aligning with the WHATWG URL standard. No other mitigation is indicated. Patch status is confirmed by the vendor advisory stating the issue is fixed in 0.0.30.
CVE-2026-53538: CWE-436: Interpretation Conflict in Kludex python-multipart
Description
A vulnerability in python-multipart prior to version 0.0.30 allows interpretation conflicts in parsing application/x-www-form-urlencoded bodies. The QuerystringParser treated the semicolon (;) as a field separator in addition to the ampersand (&), which is inconsistent with the WHATWG URL standard and modern browsers. This discrepancy can enable an attacker to smuggle extra form fields past upstream body inspection components. The issue is fixed in version 0.0.30.
CVSS v3.1
Score 3.7low
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The python-multipart library, used for streaming multipart parsing in Python, had a parsing inconsistency before version 0.0.30. Specifically, its QuerystringParser treated the semicolon character as a separator in application/x-www-form-urlencoded bodies, whereas the WHATWG URL standard and modern browsers treat only the ampersand as a separator. This mismatch creates a parser differential, allowing attackers to inject additional form fields that may bypass upstream inspection mechanisms. This vulnerability is identified as CWE-436 (Interpretation Conflict) and CWE-444 (Inconsistent Interpretation of HTTP Requests). The vulnerability is resolved in python-multipart version 0.0.30.
Potential Impact
This vulnerability allows an attacker to smuggle extra form fields past upstream body inspection components due to inconsistent parsing of field separators. While it does not directly compromise confidentiality or availability, it can lead to integrity issues by enabling injection of unexpected form fields, potentially affecting application logic or security controls relying on accurate request parsing.
Mitigation Recommendations
Upgrade python-multipart to version 0.0.30 or later, where the QuerystringParser no longer treats semicolon as a field separator, aligning with the WHATWG URL standard. No other mitigation is indicated. Patch status is confirmed by the vendor advisory stating the issue is fixed in 0.0.30.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-09T18:13:07.263Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a39735aeed863c81e396230
Added to database: 06/22/2026, 17:39:38 UTC
Last enriched: 06/22/2026, 18:09:26 UTC
Last updated: 06/23/2026, 02:16:29 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.