CVE-2026-55603: CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection') in chimurai http-proxy-middleware
http-proxy-middleware is node.js http-proxy middleware. From 3.0.4 until 3.0.7 and 4.1.1, fixRequestBody() is the library's documented helper for re-emitting a request body that was already consumed by a body parser. When the outgoing Content-Type is multipart/form-data, it rebuilds the body with handlerFormDataBodyData(), which interpolates each req.body key and value directly into the multipart wire format without neutralizing CR/LF. A \r\n inside a value (or key) lets an attacker close the current part and inject an entirely new form part. Because the proxy's own body parser saw a single opaque value, any gateway-side policy or validation performed on req.body is evaluated against a different set of fields than the upstream backend ultimately parses a request/parameter desynchronization across the trust boundary. This vulnerability is fixed in 3.0.7 and 4.1.1.
AI Analysis
Technical Summary
The http-proxy-middleware Node.js library versions >=3.0.4 <3.0.7 and >=4.1.0 <4.1.1 contain a CRLF injection vulnerability (CWE-93) in the fixRequestBody() helper function when handling multipart/form-data content types. The function rebuilds the request body by interpolating req.body keys and values directly into the multipart wire format without neutralizing CR/LF sequences. An attacker can exploit this by injecting \r\n characters in keys or values to prematurely close a multipart section and inject new form parts. This causes a mismatch between the proxy's parsed request body and the backend's parsed request body, potentially bypassing gateway-side validation or policy enforcement. The vulnerability has a CVSS 3.1 score of 7.5 (high severity) and affects the specified version ranges. It is fixed in versions 3.0.7 and 4.1.1.
Potential Impact
An attacker can exploit this vulnerability to inject additional form parts into multipart/form-data requests by including CRLF sequences in request keys or values. This leads to a desynchronization between the proxy's parsed request body and the backend's parsed request body, potentially allowing bypass of gateway-side validation or security policies. The impact includes partial confidentiality loss and high integrity impact, with no availability impact reported.
Mitigation Recommendations
Upgrade http-proxy-middleware to version 3.0.7 or later, or 4.1.1 or later, where this vulnerability is fixed. Patch status is not explicitly stated but the description confirms the vulnerability is fixed starting at these versions. Until upgraded, avoid using the fixRequestBody() helper with multipart/form-data content types or apply custom input validation to neutralize CRLF sequences in request keys and values.
CVE-2026-55603: CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection') in chimurai http-proxy-middleware
Description
http-proxy-middleware is node.js http-proxy middleware. From 3.0.4 until 3.0.7 and 4.1.1, fixRequestBody() is the library's documented helper for re-emitting a request body that was already consumed by a body parser. When the outgoing Content-Type is multipart/form-data, it rebuilds the body with handlerFormDataBodyData(), which interpolates each req.body key and value directly into the multipart wire format without neutralizing CR/LF. A \r\n inside a value (or key) lets an attacker close the current part and inject an entirely new form part. Because the proxy's own body parser saw a single opaque value, any gateway-side policy or validation performed on req.body is evaluated against a different set of fields than the upstream backend ultimately parses a request/parameter desynchronization across the trust boundary. This vulnerability is fixed in 3.0.7 and 4.1.1.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The http-proxy-middleware Node.js library versions >=3.0.4 <3.0.7 and >=4.1.0 <4.1.1 contain a CRLF injection vulnerability (CWE-93) in the fixRequestBody() helper function when handling multipart/form-data content types. The function rebuilds the request body by interpolating req.body keys and values directly into the multipart wire format without neutralizing CR/LF sequences. An attacker can exploit this by injecting \r\n characters in keys or values to prematurely close a multipart section and inject new form parts. This causes a mismatch between the proxy's parsed request body and the backend's parsed request body, potentially bypassing gateway-side validation or policy enforcement. The vulnerability has a CVSS 3.1 score of 7.5 (high severity) and affects the specified version ranges. It is fixed in versions 3.0.7 and 4.1.1.
Potential Impact
An attacker can exploit this vulnerability to inject additional form parts into multipart/form-data requests by including CRLF sequences in request keys or values. This leads to a desynchronization between the proxy's parsed request body and the backend's parsed request body, potentially allowing bypass of gateway-side validation or security policies. The impact includes partial confidentiality loss and high integrity impact, with no availability impact reported.
Mitigation Recommendations
Upgrade http-proxy-middleware to version 3.0.7 or later, or 4.1.1 or later, where this vulnerability is fixed. Patch status is not explicitly stated but the description confirms the vulnerability is fixed starting at these versions. Until upgraded, avoid using the fixRequestBody() helper with multipart/form-data content types or apply custom input validation to neutralize CRLF sequences in request keys and values.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T23:31:22.444Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a39a0f6eed863c81e6b0296
Added to database: 06/22/2026, 20:54:14 UTC
Last enriched: 06/29/2026, 21:56:17 UTC
Last updated: 08/05/2026, 00:41:15 UTC
Views: 87
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.