CVE-2026-100664
Last modified
CVE-2026-100664 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. Netty's HTTP/3 codec (io.netty:netty-codec-http3) versions 4.2.2.Final through 4.2.17.Final builds the HTTP/3 :authority pseudo-header from the HTTP/1 Host header before considering the authority of an absolute-form HTTP/1 request-target. In HttpConversionUtil.toHttp3Headers(HttpMessage, boolean) — reached via Http3FrameToHttpObjectCodec(false) — a non-empty Host header takes precedence over the request-target authority, contrary to the HTTP/1.1 rule that a server receiving an absolute-form request-target must ignore the Host header.
Description
Netty's HTTP/3 codec (io.netty:netty-codec-http3) versions 4.2.2.Final through 4.2.17.Final builds the HTTP/3 :authority pseudo-header from the HTTP/1 Host header before considering the authority of an absolute-form HTTP/1 request-target. In HttpConversionUtil.toHttp3Headers(HttpMessage, boolean) — reached via Http3FrameToHttpObjectCodec(false) — a non-empty Host header takes precedence over the request-target authority, contrary to the HTTP/1.1 rule that a server receiving an absolute-form request-target must ignore the Host header. In a Netty-based HTTP/1-to-HTTP/3 gateway, proxy, or protocol bridge, a remote client can send a request such as "GET https://trusted.example/admin HTTP/1.1" with "Host: attacker.example", causing components that validate, authorize, or route on the RFC-defined request-target authority to reach a different decision than the upstream HTTP/3 peer, which receives :authority derived from the conflicting Host header. This authority confusion can affect virtual-host routing, allow-list checks, backend selection, cache keys, and URL generation. The advisory reports integrity impact only (no code execution, memory corruption, or availability impact). Fixed in 4.2.18.Final.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| netty | netty | >= 4.2.2.Final, < 4.2.18.Final |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-100664?
How severe is CVE-2026-100664?
How do I fix CVE-2026-100664?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-100659Netty's HTTP/3 codec (io.netty:netty-codec-http3) in version…6.5
- CVE-2026-10066A security vulnerability has been detected in Shibby Tomato …8.8
- CVE-2026-100660Netty's HTTP/3 codec (io.netty:netty-codec-http3) from 4.2.0…7.5
- CVE-2026-100661Netty's HTTP/3 codec (io.netty:netty-codec-http3) versions 4…7.5
- CVE-2026-100662Netty's HTTP/3 codec (io.netty:netty-codec-http3) versions 4…7.5
- CVE-2026-100663Netty's HTTP/3 codec (io.netty:netty-codec-http3) from 4.2.2…7.5
- CVE-2026-100665Netty versions from 4.2.11.Final before 4.2.18.Final contain…7.5
- CVE-2026-100666Netty's HttpServerCodec (io.netty:netty-codec-http) in versi…7.3
- CVE-2026-100667grav-plugin-login (the Grav CMS Login plugin) versions >= 3.…5.3
- CVE-2026-100668Grav 2.0.0 through 2.0.24 contain a Twig content sandbox esc…6.5
- CVE-2026-100669Grav before 2.0.25 ships web server configuration samples wh…7.5
- CVE-2026-10067A vulnerability was detected in Shibby Tomato 1.28. Impacted…8.8
Are you affected by CVE-2026-100664?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
