VulnerabilityPublished 13 Aug 2026Updated 4 Nov 2026

CVE-2026-42561: Mcp proxy · python-multipart has Denial of Service via unbounded multipart part headers

Affects mcp-proxySource GCVE Database

Compare

Authoritative record:CVE-2026-42561· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.11.0_4 soon.

Data as of 4 Nov 2026, 07:01 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 0.11.0_4

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 May 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade mcp-proxy to 0.11.0_4.

Affected software

Product	Affected	Fixed in
Homebrewmcp-proxy`pkg:brew/mcp-proxy`Other threats	Affected >=0.8.2 <0.11.0_4	Fixed in 0.11.0_4

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.11.0_4 or later to apply the official fix. If immediate upgrade is not possible, mitigate exposure by enforcing request body size limits at the server, proxy, or framework level. Note that this mitigation does not fully address the vulnerability since affected versions still parse multipart headers without limits.

Description

python-multipart versions from 0.8.2 up to but not including 0.11.0_4 contain a denial of service vulnerability in multipart part header parsing. The MultipartParser did not limit the number or size of headers, allowing attackers to cause excessive CPU usage by sending requests with many repeated headers or very large header values. This can lead to CPU exhaustion and delays in ASGI applications using frameworks like Starlette or FastAPI. The issue is fixed in version 0.11.0_4.

Impact

Applications using affected versions of python-multipart that parse attacker-controlled multipart/form-data can suffer CPU exhaustion. This leads to worker or event-loop delays in ASGI applications such as those built with Starlette or FastAPI, potentially degrading service availability or causing denial of service conditions.

Summary

The python-multipart library has a denial of service vulnerability (CVE-2026-42561) due to unbounded multipart part header parsing. Specifically, the MultipartParser lacked limits on the number of part headers and the size of individual headers when processing multipart/form-data requests. An attacker can exploit this by sending a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU consumption before the request is rejected or completed. The affected parser states include HEADER_FIELD_START, HEADER_FIELD, HEADER_VALUE_START, HEADER_VALUE, and HEADER_VALUE_ALMOST_DONE. The vulnerability affects versions >=0.8.2 and <0.11.0_4 of python-multipart and is fixed in 0.11.0_4 by enforcing default limits on header count and size.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 07:01 UTC

Technical details

References

Community reviews

Related threats