CRLF Injection Affecting n8n package, versions <2.28.3-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.27% (19th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-N8N-17402042
  • published23 Jun 2026
  • disclosed22 Jun 2026

Introduced: 22 Jun 2026

CVE-2026-55603  (opens in a new tab)
CWE-93  (opens in a new tab)

How to fix?

Upgrade Minimos:latest n8n to version 2.28.3-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream n8n package and not the n8n package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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 Base Scores

version 3.1