Netty 4.2.0 through 4.2.17 HTTP/3 Request Routing Bypass
Netty's HTTP/3 codec (io.netty:netty-codec-http3) in versions 4.2.0.Final through 4.2.17.Final does not enforce the RFC 9114 requirement that the :authority pseudo-header field and a literal host header field, when both present, carry the same value. A remote unauthenticated peer can send a single HEADERS frame containing both fields with differing, attacker-controlled values; the request is accepted and delivered to the application with two conflicting authorities, allowing routing, virtual-host, and access-control decisions to be bypassed when different components in the request path consult different fields. This issue is fixed in 4.2.18.Final.
CVE-2026-100659
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-100659
netty
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "netty",
"product": "netty",
"versions": [
{
"status": "affected",
"version": "4.2.0.Final",
"lessThan": "4.2.18.Final",
"versionType": "custom"
},
{
"status": "unaffected",
"version": "4.2.18.Final",
"versionType": "custom"
}
],
"packageURL": "pkg:maven/io.netty/netty-codec-http3",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-100659
Source reference:
/cveMetadata/cveId
Publisher severity
medium
Source reference: /containers/cna/metrics
- Event
- #3289 · Revision 1
- Added to Heist Feed
- Publisher date