cycode · python-multipart: Quadratic-time querystring parsing with semicolon separators causes CPU denial of service
Affects cycodeSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 3.16.0 soon.
Data as of 19 Nov 2026, 19:48 UTC
- Patch
- Available – fixed in 3.16.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation 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 18 Nov 2026.
What to do
Upgrade cycode to 3.16.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewcycodepkg:brew/cycodeOther 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 3.16.0 or later. This version fixes the vulnerability by treating only '&' as a field separator and performing parsing in linear time, preventing excessive CPU consumption. No other mitigation is required as the fix addresses the root cause.
Description
A vulnerability in python-multipart's QuerystringParser causes quadratic-time parsing of application/x-www-form-urlencoded bodies using semicolon separators, leading to excessive CPU consumption and potential denial of service. The issue arises because the parser repeatedly scans the entire remaining buffer for '&' before checking for ';', resulting in O(B^2) complexity for bodies with many semicolon-separated fields and no ampersands. This can block worker processes for seconds per crafted request, degrading service availability. The flaw affects versions >=3.2.0 and <3.16.0 and is fixed in version 3.16.0.