CVE-2026-53538: python-multipart · Semicolon treated as querystring field separator enables parameter smuggling
Affects mcp-atlassianSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 3.7 Low : upgrade to 0.21.1_8 when convenient.
Data as of 18 Nov 2026, 19:24 UTC
- Patch
- Available – fixed in 0.21.1_8
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation 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 17 Nov 2026.
What to do
Upgrade mcp-atlassian to 0.21.1_8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewmcp-atlassianpkg:brew/mcp-atlassianOther 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 0.21.1_8 or later. This version corrects the parsing behavior to treat only '&' as a field separator in application/x-www-form-urlencoded bodies, aligning with the WHATWG URL standard and eliminating the parser differential. No other mitigation actions are required as the fix fully addresses the issue.
Description
The python-multipart library's QuerystringParser incorrectly treats the semicolon (';') as a field separator in application/x-www-form-urlencoded bodies, contrary to the WHATWG URL standard which only recognizes '&' as a separator. This discrepancy allows HTTP parameter pollution, enabling attackers to smuggle extra or overriding form fields past upstream components that follow the standard. The issue affects versions from 0.11.9 up to but not including 0.21.1_8. A fix is available in version 0.21.1_8 and later, which aligns parsing behavior with the WHATWG standard by treating ';' as ordinary data rather than a separator.