mcp-proxy · python-multipart: Quadratic-time querystring parsing with semicolon separators causes CPU denial of service
Affects mcp-proxySource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 0.12.0_2 soon.
Data as of 4 Nov 2026, 07:00 UTC
- Patch
- Available – fixed in 0.12.0_2
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 3 Nov 2026.
What to do
Upgrade mcp-proxy to 0.12.0_2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewmcp-proxypkg:brew/mcp-proxyOther 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 0.12.0_2 or later. This version changes the parser to treat only '&' as a field separator, eliminating the quadratic-time parsing issue and reducing CPU consumption to linear time. No other mitigation is required.
Description
A vulnerability in python-multipart's QuerystringParser causes quadratic-time parsing of application/x-www-form-urlencoded bodies that use semicolon separators. This leads to excessive CPU consumption and potential denial of service when processing crafted request bodies with many semicolon-separated fields. The issue affects versions from 0.8.2 up to but not including 0.12.0_2. The vulnerability is fixed in version 0.12.0_2 by changing the parser to only treat '&' as a field separator, making parsing linear in time.