Skip to main content
VulnerabilityPublished Updated

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

Affects semgrepSource GCVE Database

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

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

Data as of 19 Nov 2026, 19:38 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.165.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 semgrep to 1.165.0.

Affected software

ProductAffectedFixed in
Homebrewsemgreppkg:brew/semgrepOther threatsAffected
  • >=1.137.0 <1.165.0
Fixed in
  • 1.165.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 1.165.0 or later. This version ignores RFC 2231/5987 extended parameters (name*, filename*, and their continuations), ensuring the plain name and filename parameters remain authoritative, consistent with RFC 7578 §4.2 which forbids these extended parameters in multipart/form-data. No other mitigation is required if upgraded.

Description

A vulnerability in python-multipart allows an attacker to exploit differences in how Content-Disposition headers with RFC 2231/5987 extended parameters are parsed. The extended parameters (such as filename* and name*) override the plain parameters, which can cause discrepancies between upstream inspectors and the backend application. This can lead to bypassing access controls or path traversal if the application uses the smuggled filename without proper sanitization. The issue affects versions >=1.137.0 and <1.165.0 and is fixed in version 1.165.0.

References

Community reviews

Loading reviews…