CVE-2026-24486

Python-Multipart has Arbitrary File Write via Non-Default Configuration

HIGH
7.5
CVSS Score
Published: January 27, 2026 at 12:34 AM UTC
Updated: August 7, 2026 at 12:41 PM UTC
9 products affected across 3 vendorsPython MultipartSatelliteOpenShift AI

Using python-multipart by Kludex?

Get instant alerts when new vulnerabilities affect python-multipart - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 2%
SSVC
No known exploit

Description

Python-Multipart is a streaming multipart parser for Python. Prior to version 0.0.22, a Path Traversal vulnerability exists when using non-default configuration options `UPLOAD_DIR` and `UPLOAD_KEEP_FILENAME=True`. An attacker can write uploaded files to arbitrary locations on the filesystem by crafting a malicious filename. Users should upgrade to version 0.0.22 to receive a patch or, as a workaround, avoid using `UPLOAD_KEEP_FILENAME=True` in project configurations.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.0.22
Affected range stops below 0.0.22, so it looks safe — our inference, not a vendor statement
v < 0.0.22
Affected range stops below 0.0.22, so it looks safe — our inference, not a vendor statement
All versions
Vendor states this is fixed in 1772160593 (unaffected)
Vendor states this is fixed in 1772160625 (unaffected)
Vendor states this is fixed in 1772204398 (unaffected)
Vendor states this is fixed in 1772429277 (unaffected)
Vendor states this is fixed in 2 (unaffected)
All versions
Vendor states this is fixed in 1770956034 (unaffected)
Vendor states this is fixed in 1772093278 (unaffected)
Vendor states this is fixed in 1776259063 (unaffected)
Vendor states this is fixed in 1776338381 (unaffected)
Vendor states this is fixed in 1778264363 (unaffected)
Vendor states this is fixed in 1783998774 (unaffected)
Vendor states this is fixed in 1783998857 (unaffected)
Vendor states this is fixed in 1769520238 (unaffected)
Vendor states this is fixed in 1784554123 (unaffected)
Vendor states this is fixed in 1784834402 (unaffected)
All versions

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (17)

x_refsource_CONFIRMExploitVendor Advisory
Source: cverecord
https://github.com/Kludex/python-multipart/security/advisories/GHSA-wp53-j4wj-2cfg
x_refsource_MISCProductRelease Notes
Source: cverecord
https://github.com/Kludex/python-multipart/releases/tag/0.0.22
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:10184
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:1504
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:19712
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:3461
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:3462

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-22

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card