CVE-2026-24486
Path traversal in Python-Multipart before 0.0.22 allows arbitrary file write via crafted filename.
Is CVE-2026-24486 being exploited?
Not confirmed. CVE-2026-24486 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.2% probability of exploitation in the next 30 days.
How severe is CVE-2026-24486?
CVE-2026-24486 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-24486?
Yes. A fix has been recorded for CVE-2026-24486. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-24486 affect?
CVE-2026-24486 affects Python-Multipart. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-24486?
Upgrade to 0.0.22; disable UPLOAD_KEEP_FILENAME; restrict UPLOAD_DIR.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary file writes to server filesystem via uploads; may lead to remote code execution if uploaded files are served or executed.
Patch when possible
- affected< 0.0.22
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.