CVE-2026-53537: python-multipart · Content-Disposition parameter smuggling via RFC 2231/5987 extended parameters
Affects mcp-atlassianSource GCVE Database
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, which ignores RFC 2231/5987 extended parameters (name*, filename*, and their continuations) so that the plain name and filename parameters remain authoritative. This aligns with RFC 7578 §4.2, which forbids filename* in multipart/form-data. No other mitigation is required as the fix addresses the root cause.
Description
The python-multipart library improperly handles RFC 2231/5987 extended parameters in Content-Disposition headers for multipart/form-data. It prioritizes extended parameters (e.g., filename* or name*) over plain parameters, which conflicts with RFC 7578 that forbids these extended forms in multipart/form-data. This discrepancy can be exploited to smuggle different field names or filenames past upstream inspectors, potentially bypassing access controls or causing path traversal if filenames are unsafely used. The issue affects several parsing APIs and frameworks like Starlette/FastAPI. A fix is available in python-multipart version 0.21.1_8 and later, which ignores these extended parameters to comply with RFC 7578.
References
- github.com/Kludex/python-multipart/security/advisories/GHSA-vffw-93wf-4j4q (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-53537 (opens in a new tab)
- github.com/Kludex/python-multipart (opens in a new tab)
- github.com/advisories/GHSA-vffw-93wf-4j4q (opens in a new tab)
- github.com/pypa/advisory-database/blob/main/vulns/python-multipart/PYSEC-2026-3041.yaml (opens in a new tab)
- pypi.org/project/python-multipart (opens in a new tab)