form-data does not escape CR/LF/quote in multipart field names and filenames (CRLF injection)

Summary

form-data is a library for creating readable multipart/form-data streams. In versions through 4.0.5, the `field` argument to `FormData#append` and the `filename` option are concatenated verbatim into the `Content-Disposition` header without escaping carriage return (CR), line feed (LF), or double-quote (") characters. An application that passes attacker-controlled data as a field name or filename (for example, an API gateway that turns JSON object keys into multipart field names) allows the attacker to terminate the header line and inject additional headers, or to smuggle entire additional multipart parts, into the request the application forwards to a backend. This can let the attacker add or override form fields (e.g. set `is_admin=true`) seen by the downstream parser. This is an instance of CWE-93 (CRLF injection). The fix escapes CR, LF, and `"` as `%0D`, `%0A`, and `%22` in field names and filenames, matching the serialization browsers use per the WHATWG HTML multipart/form-data encoding algorithm. Exploitation requires the consuming application to use untrusted input as a field name or filename; applications that use only fixed/trusted field names are not affected. Fixed in 2.5.6, 3.0.5, and 4.0.6.

Timeline

1. Jun 12, 2026, 6:01 PM UTCCVE published
2. Jun 12, 2026, 7:04 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: yes · Technical impact: partial

3. Sep 11, 2026, 12:08 PM UTCRecord last updated

Affected versions

• form-data

  fixed in 2.5.6; From 3.0.0 · fixed in 3.0.5; From 4.0.0 · fixed in 4.0.6

• form-datanpm

  fixed in 2.5.6

• form-datanpm

  From 3.0.0 · fixed in 3.0.5

• form-datanpm

  From 4.0.0 · fixed in 4.0.6

References 7