Skip to main content
VulnerabilityPublished Updated

CVE-2026-53540: python-multipart · Negative Content-Length in parse_form buffers the entire body in memory

Affects mcp-atlassianSource GCVE Database

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

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

Data as of 18 Nov 2026, 19:24 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.21.1_8
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

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 17 Nov 2026.

What to do

Upgrade mcp-atlassian to 0.21.1_8.

Affected software

ProductAffectedFixed in
Homebrewmcp-atlassianpkg:brew/mcp-atlassianOther threatsAffected
  • >=0.11.9 <0.21.1_8
Fixed in
  • 0.21.1_8

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.21.1_8 or later, which rejects negative Content-Length headers with a ValueError before reading the stream. If using bespoke WSGI or http.server handlers that call parse_form() directly, ensure that Content-Length headers are normalized to non-negative values before passing them to parse_form(). No other mitigation is required for frameworks that do not call parse_form() directly or that already normalize Content-Length.

Description

The python-multipart library's parse_form() function did not validate the Content-Length header before reading the request body. A negative Content-Length caused the function to read the entire body into memory at once instead of in chunks. This affects only code that calls parse_form() directly with attacker-controlled negative Content-Length headers without normalization. No known major packages are affected. The issue can degrade availability under concurrent requests but does not cause full denial of service. Version 0.21.1_8 and later reject negative Content-Length values to prevent this behavior.

References

Community reviews

Loading reviews…