Skip to main content
VulnerabilityPublished Updated

CVE-2026-24486: Cycode · Python-Multipart has Arbitrary File Write via Non-Default Configuration

Affects cycodeSource GCVE Database

0
Compare
Authoritative record:CVE-2026-24486· High 8.6

Public exploit available (Exploit-DB) · CVSS 8.6 High : upgrade to 3.8.9_1 as a priority.

Data as of 19 Nov 2026, 19:48 UTC

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

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 27 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 4 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 17 minutes after disclosure

  4. First Exploit-DB entry (opens in a new tab)

    Python-Multipart 0.0.22 - Path Traversal

    , 93 days after disclosure

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.8.9_1.

Affected software

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

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Python-Multipart version 3.8.9_1 or later. Alternatively, avoid using the configuration option UPLOAD_KEEP_FILENAME=True with UPLOAD_DIR set. The default configuration is not vulnerable.

Description

A path traversal vulnerability in the Python-Multipart library allows arbitrary file write when using a non-default configuration with UPLOAD_DIR set and UPLOAD_KEEP_FILENAME=True. This occurs because the filename can start with a slash, causing os.path.join to ignore the intended upload directory and write files to arbitrary filesystem locations. The vulnerability affects versions from 3.2.0 up to but not including 3.8.9_1. The default configuration is not vulnerable. The issue is fixed in version 3.8.9_1.

References

Community reviews

Loading reviews…