Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-28356: CWE-1333: Inefficient Regular Expression Complexity in defnull multipart

0
High
VulnerabilityCVE-2026-28356cvecve-2026-28356cwe-1333
Published: Thu Mar 12 2026 (03/12/2026, 16:45:01 UTC)
Source: CVE Database V5
Vendor/Project: defnull
Product: multipart

Description

multipart is a fast multipart/form-data parser for python. Prior to 1.2.2, 1.3.1 and 1.4.0-dev, the parse_options_header() function in multipart.py uses a regular expression with an ambiguous alternation, which can cause exponential backtracking (ReDoS) when parsing maliciously crafted HTTP or multipart segment headers. This can be abused for denial of service (DoS) attacks against web applications using this library to parse request headers or multipart/form-data streams. The issue is fixed in 1.2.2, 1.3.1 and 1.4.0-dev.

AI-Powered Analysis

AILast updated: 03/12/2026, 18:49:29 UTC

Technical Analysis

The vulnerability CVE-2026-28356 affects the multipart Python library developed by defnull, which is used for parsing multipart/form-data in HTTP requests. The root cause is an inefficient regular expression in the parse_options_header() function within multipart.py. This regex contains an ambiguous alternation pattern that can cause exponential backtracking when processing maliciously crafted multipart headers. Exponential backtracking leads to excessive CPU usage, effectively allowing an attacker to perform a Regular Expression Denial of Service (ReDoS) attack. The vulnerability impacts multipart versions earlier than 1.2.2 and versions from 1.3.0 up to but not including 1.3.1. The attack vector is network-based, requiring no privileges or user interaction, making it straightforward to exploit remotely. The vulnerability does not affect confidentiality or integrity but severely impacts availability by causing application or service slowdown or crash. The issue was publicly disclosed in March 2026 and has been addressed in multipart releases 1.2.2, 1.3.1, and 1.4.0-dev. No public exploit code or active exploitation has been reported to date, but the nature of the vulnerability makes it a significant risk for denial of service in web applications relying on this library for multipart/form-data parsing.

Potential Impact

This vulnerability primarily impacts the availability of web applications that use the vulnerable versions of the multipart library for processing HTTP multipart/form-data requests. Attackers can remotely trigger excessive CPU consumption by sending specially crafted multipart headers, leading to denial of service conditions such as application slowdowns, crashes, or unresponsiveness. This can disrupt business operations, degrade user experience, and potentially cause cascading failures in dependent systems. Since the vulnerability requires no authentication or user interaction, it can be exploited by unauthenticated remote attackers, increasing the risk surface. Organizations running Python web applications or APIs that handle file uploads or multipart requests using the affected versions are at risk. The impact is especially critical for high-availability services, cloud-hosted applications, and APIs exposed to the internet. While no confidentiality or integrity loss is involved, the denial of service can be leveraged as part of larger attack campaigns or to distract from other malicious activities.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately upgrade the multipart library to version 1.2.2, 1.3.1, or later, including 1.4.0-dev, where the issue is resolved. If upgrading is not immediately feasible, consider implementing input validation or rate limiting on multipart/form-data requests to reduce the risk of malicious payloads triggering the ReDoS condition. Web application firewalls (WAFs) can be configured to detect and block suspicious multipart header patterns or unusually large multipart requests. Monitoring CPU usage and application performance metrics can help detect potential exploitation attempts. Developers should review and test multipart parsing logic to ensure it does not rely on vulnerable regex patterns. Additionally, adopting fuzz testing and regular expression complexity analysis tools during development can prevent similar issues. Finally, maintain an inventory of all Python dependencies and apply security patches promptly to reduce exposure to known vulnerabilities.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-26T18:38:13.890Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69b30a4d2f860ef943dbc483

Added to database: 3/12/2026, 6:47:41 PM

Last enriched: 3/12/2026, 6:49:29 PM

Last updated: 3/14/2026, 12:57:29 AM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses