Skip to main content
VulnerabilityPublished Updated

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

Affects cycodeSource GCVE Database

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

Not known to be exploited · CVSS 3.7 Low : upgrade to 3.16.0 when convenient.

Data as of 19 Nov 2026, 19:49 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.16.0
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 18 Nov 2026.

What to do

Upgrade cycode to 3.16.0.

Affected software

ProductAffectedFixed in
Homebrewcycodepkg:brew/cycodeOther threatsAffected
  • >=3.2.0 <3.16.0
Fixed in
  • 3.16.0

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 3.16.0 or later. This version ignores RFC 2231/5987 extended parameters (name*, filename*, and their continuations), ensuring that only the plain name and filename parameters are authoritative, consistent with RFC 7578 §4.2. No other mitigation is required as the fix addresses the root cause.

Description

A vulnerability in python-multipart allows an attacker to smuggle different Content-Disposition parameter values by exploiting RFC 2231/5987 extended parameter decoding. This causes a mismatch between what upstream inspectors see and what the backend application receives, potentially bypassing field name or filename based controls. The issue affects multipart/form-data parsing and can lead to path traversal or control byte confusion if the application uses these values unsafely. The vulnerability is fixed in python-multipart version 3.16.0.

References

Community reviews

Loading reviews…