Skip to main content
VulnerabilityPublished Updated

CVE-2026-53537: python-multipart · Content-Disposition parameter smuggling via RFC 2231/5987 extended parameters

Affects mcp-atlassianSource GCVE Database

0
Compare
Authoritative record:CVE-2026-53537· Low 3.7

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

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Homebrewmcp-atlassianpkg:brew/mcp-atlassianOther threatsAffected
  • >=0.11.9 <0.21.1_8
Fixed in
  • 0.21.1_8

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

Community reviews

Loading reviews…