Netty: CRLF Injection via Multipart Filename in Netty HttpPostRequestEncoder (netty netty)

CVE-2026-59921
MEDIUM 5.7

At a glance

Source
NVD
EPSS
EPSS 0.46 % · percentile 40 ()
State
PUBLISHED
Published
Updated
Assigner
GitHub_M
NVD status
Analyzed

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.

Weaknesses (CWE)

  • CWE-93 — Improper Neutralization of CRLF Sequences

References

Scores

VersionScoreVectorScored by
CVSS 3.1MEDIUM 5.7CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NGitHub_M
CVSS 3.1MEDIUM 5.7CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NNVD · security-advisories@github.com (Secondary)
CVSS 3.1MEDIUM 6.5CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NNVD · nvd@nist.gov (Primary)

Advisories

European references

CERT-FR advisories

Affected configurations (NVD CPE)

Affected products

ProductVersions
netty · nettyaffected >= 4.2.0.Final, < 4.2.16.Final ; affected < 4.1.136.Final

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
CERT-FR (ANSSI)Licence Ouverte / Etalab 2.0
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD