CVE-2026-42584CRITICAL 9.1EPSS p23.5%

CVE-2026-42584CVE-2026-42584

Description

Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, HttpClientCodec pairs each inbound response with an outbound request by queue.poll() once per response, including for 1xx. If the client pipelines GET then HEAD and the server sends 103, then 200 with GET body, then 200 for HEAD, the queue pairs HEAD with the first 200. The HEAD rule then skips reading that message’s body, so the GET entity bytes stay on the stream and the following 200 is parsed from the wrong offset. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.

Scoring

CVSS 3.19.1 (CRITICAL)
VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS0.32% probability of exploitation · percentile 23.5% · 2026-06-19T12:03:05Z
Published2026-05-13
Last modified2026-05-18

Underlying weaknesses· 1

CWE-444

References

  1. https://github.com/netty/netty/security/advisories/GHSA-57rv-r2g8-2cj3
  2. https://github.com/netty/netty/security/advisories/GHSA-57rv-r2g8-2cj3

1

TypeTargetConfidenceTier
WeaknessInconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')cwe-4440%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CVE
CVE-2026-42581
CVE
CVE-2026-42579
CVE
CVE-2026-48480
CVE
CVE-2026-41715
CVE
CVE-2026-48040
CVE
CVE-2026-28368
Sourced from NVD + FIRST.org EPSS. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.