CVE-2026-59921

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this weekElevated
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.7Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.7
EG Score
5.7(medium)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity57% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 28, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

CRLF Injection via Multipart Filename in Netty HttpPostRequestEncoder · Advisory · netty/netty · GitHub

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnetty-codec-http2026-07-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.netty:netty-codec-http4.0.0.Alpha1 ... 4.1.99.Final (229 versions)4.1.136.Final

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-30 16:46 UTCEG score recompute
  2. 2026-07-30 16:46 UTCVendor advisory
  3. 2026-07-30 16:28 UTCEPSS rescore
  4. 2026-07-30 01:30 UTCEPSS rescore
  5. 2026-07-30 01:30 UTCEPSS rescore
  6. 2026-07-29 18:31 UTCEG score recompute
  7. 2026-07-29 17:37 UTCEG score recompute
  8. 2026-07-29 13:19 UTCEG score recompute
  9. 2026-07-28 23:23 UTCEG score recompute
  10. 2026-07-27 09:13 UTCEG score recompute
  11. 2026-07-23 03:21 UTCEG score recompute
  12. 2026-07-22 22:26 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-59921?
CVE-2026-59921 is a medium vulnerability published on July 22, 2026. 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…
When was CVE-2026-59921 disclosed?
CVE-2026-59921 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59921 actively exploited?
CVE-2026-59921 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.6% of all scored CVEs.
What is the CVSS score of CVE-2026-59921?
CVE-2026-59921 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2026-59921?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59921, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59921

Explore →

Is Your Infrastructure Affected by CVE-2026-59921?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.