Skip to main content
VulnerabilityPublished Updated

CVE-2026-53538: python-multipart · Semicolon treated as querystring field separator enables parameter smuggling

Affects cycodeSource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-53538· 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:48 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, which corrects the parsing behavior to treat only '&' as a field separator in compliance with the WHATWG URL standard. This update prevents parameter smuggling by ensuring consistent parsing between intermediaries and backend components.

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 the ampersand (&) as a separator. This discrepancy allows attackers to smuggle additional or overriding form fields past upstream components that follow the standard, potentially causing the backend to receive parameters not seen by intermediaries. The issue affects versions from 3.2.0 up to but not including 3.16.0 and is fixed in version 3.16.0.

References

Community reviews

Loading reviews…