What’s Vulnerable › Vulnerabilities

CVE-2026-59921: Netty: CRLF Injection via Multipart Filename in Netty HttpPostRequestEncoder

• Severity: medium (CVSS 6.5 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.5% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-07-28 · updated 2026-08-07
• Weakness: CWE-93

Description

Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, HttpPostRequestEncoder constructs multipart HTTP request bodies by directly concatenating user-supplied filenames and field names into Content-Disposition MIME headers without validating or sanitizing CRLF characters (\r\n). Since MIME headers are delimited by CRLF, an attacker who controls the filename can inject arbitrary MIME headers into the multipart body part. The root cause is that neither the encoder nor the FileUpload implementations' setFilename() methods, which only check for null, neutralize CRLF characters before the filename is embedded into the header. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.

Affected products

• netty: before 4.1.136; from 4.2.0 before 4.2.16 — fixed in 4.1.136, 4.2.16

How to fix

Upgrade to a fixed version: netty 4.1.136, 4.2.16. Check the vendor advisory for mitigations.

References

• https://github.com/netty/netty/security/advisories/GHSA-gcjf-9mgh-3p7g
• https://github.com/netty/netty/security/advisories/GHSA-gcjf-9mgh-3p7g

Get alerted when CVE-2026-59921 or the next vulnerability affects your stack