Skip to main content
VulnerabilityPublished Updated

CVE-2026-40347: Cycode · python-multipart affected by Denial of Service via large multipart preamble or epilogue data

Affects cycodeSource GCVE Database

0
Compare
Authoritative record:CVE-2026-40347· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.13.0_1 when convenient.

Data as of 19 Nov 2026, 19:49 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.13.0_1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Apr 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.13.0_1.

Affected software

ProductAffectedFixed in
Homebrewcycodepkg:brew/cycodeOther threatsAffected
  • >=3.2.0 <3.13.0_1
Fixed in
  • 3.13.0_1

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.13.0_1 or later. This version includes fixes that optimize parsing by skipping unnecessary processing of leading CR/LF bytes and immediately discarding epilogue data after the closing boundary, preventing excessive CPU consumption from crafted multipart requests.

Description

A denial of service vulnerability in python-multipart allows attackers to send crafted multipart/form-data requests with large preamble or epilogue sections, causing excessive CPU consumption during parsing. This degrades availability by slowing request handling but does not typically cause a full application outage. The issue is fixed in version 3.13.0_1.

References

Community reviews

Loading reviews…