CVE-2023-46136: Werkzeug vulnerable to high resource usage when parsing multipart/form-data containing a large part with CR/LF character at the beginning
Werkzeug is a comprehensive WSGI web application library. In versions on the 3.x branch prior to 3.0.1 and on the 2.x branch prior to 2.3.8, if an upload of a file that starts with CR or LF and then is followed by megabytes of data without these characters: all of these bytes are appended chunk by chunk into internal bytearray and lookup for boundary is performed on growing buffer. This allows an attacker to cause a denial of service by sending crafted multipart data to an endpoint that will parse it. The amount of CPU time required can block worker processes from handling legitimate requests. This vulnerability has been patched in version 3.0.1 and 2.3.8.
Security readout for executives and security teams
Plain-English summary
Werkzeug could spend excessive CPU parsing specially shaped multipart uploads. An attacker who can reach an endpoint that parses such data could tie up worker processes, causing denial of service for legitimate users. The sources identify patched Werkzeug releases: 2.3.8 and 3.0.1.
Executive priority
Treat as high priority for affected web services because a relatively simple request pattern can degrade availability. Remediate first on customer-facing upload or form-processing applications.
Technical view
Affected Werkzeug 2.x before 2.3.8 and 3.x before 3.0.1 append multipart data into a growing bytearray and repeatedly search for boundaries when a part begins with CR or LF followed by large data. This can block WSGI workers through high CPU usage.
Likely exposure
Python web applications using Werkzeug directly or through frameworks are exposed if they run affected versions and accept multipart/form-data parsing, especially file upload or form submission routes.
Exploitation context
The provided bundle does not establish active exploitation, and KEV is false. Exploitation requires the ability to send crafted multipart data to an endpoint that parses it; the CVSS vector supplied indicates adjacent access and low privileges.
Researcher notes
The advisory describes a parser-level resource exhaustion issue, not data theft. Validate exposure by dependency version and multipart parsing reachability. Avoid assuming exploit activity or affected downstream products beyond the cited NetApp advisory.
Mitigation direction
Upgrade Werkzeug 2.x deployments to version 2.3.8 or later.
Upgrade Werkzeug 3.x deployments to version 3.0.1 or later.
Review Pallets advisory and downstream vendor guidance for deployment-specific actions.
Prioritize internet-facing or business-critical services that parse multipart/form-data.
Validation and detection
Check dependency lockfiles, SBOMs, containers, and runtime environments for Werkzeug versions.
Map endpoints that accept multipart/form-data or file uploads.
Confirm production artifacts use Werkzeug 2.3.8, 3.0.1, or later.
Review monitoring for request worker saturation or CPU spikes around upload traffic.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Inefficient Algorithmic Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.