Loading vulnerability…
CVE-2026-24486 affects Python-Multipart, a streaming multipart parser for Python. In versions prior to 0.0.22, a path traversal vulnerability exists when the library is used with the non-default configuration options UPLOAD_DIR and UPLOAD_KEEP_FILENAME=True. Under this configuration, attacker-controlled filenames from multipart uploads are preserved and used when writing files to disk, allowing a crafted filename containing traversal sequences to escape the intended upload directory and cause files to be written to arbitrary filesystem locations. The issue is specifically associated with upload handling that flushes files to disk rather than keeping them only in memory.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
UPLOAD_KEEP_FILENAME=True. Do not rely on user-supplied filenames when persisting uploads to disk. Constrain uploads to a dedicated safe directory and sanitize and normalize filenames before use. Because the issue is triggered when uploads are flushed to disk, reducing or reviewing conditions under which uploads exceed MAX_MEMORY_FILE_SIZE may also reduce exposure, though this is not a substitute for patching.Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.