CVE-2026-100664

Netty 4.2.2 through 4.2.17 HTTP/1 Host Header Authority Confusion

Published Sep 26, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Netty's HTTP/3 codec builds the :authority pseudo-header from the HTTP/1 Host header before honoring the authority value in an absolute-form HTTP request-target, violating RFC 9110. This allows a remote client to supply a Host header that differs from the request-target authority. The resulting authority confusion can mislead routing, caching, and authorization logic, enabling violations of virtual-host isolation, allow-list checks, or backend selection. The weakness is an input validation problem (CWE-20) and the improper construction of the pseudo-header (CWE-444), and results only in integrity impact; it does not enable code execution or crash the server.

Affected Systems

The flaw affects Netty and its HTTP/3 codec module (io.netty:netty-codec-http3) across versions 4.2.2.Final through 4.2.17.Final. It is fixed in 4.2.18.Final and later releases.

Risk and Exploitability

With a CVSS score of 8.7, the vulnerability is considered high severity. No EPSS data is available, so the current exploitation probability is unknown, but the flaw is not listed in the CISA KEV catalog. Attackers can exploit it remotely by sending a crafted HTTP/1 request to a Netty-based gateway, proxy, or protocol bridge that forwards traffic to an HTTP/3 backend. Successful exploitation could lead to misrouting or unauthorized access to protected resources, depending on how the application uses the :authority header.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Netty and netty-codec-http3 to version 4.2.18.Final or newer.
  • If an immediate upgrade is not possible, configure the gateway to reject HTTP/1 requests whose Host header does not match the authority of an absolute-form request-target.
  • Apply input validation on the :authority header in the Netty pipeline to ensure it reflects the request-target authority before forwarding to HTTP/3.

Generated by OpenCVE AI on September 27, 2026 at 13:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Netty 4.2.2 through 4.2.15 HTTP/1 Host Header Authority Confusion Netty 4.2.2 through 4.2.17 HTTP/1 Host Header Authority Confusion
Type Values Removed Values Added
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.
Title Netty 4.2.2 through 4.2.15 HTTP/1 Host Header Authority Confusion
First Time appeared Netty
Netty netty
Weaknesses CWE-20
CPEs cpe:2.3:a:netty:netty:*:*:*:*:*:*:*:*
Vendors & Products Netty
Netty netty
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-444

    Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 28, 2026, 4:47 PM
Reserved
Sep 26, 2026, 2:33 AM
Status
Deferred
Published
Sep 26, 2026, 2:16 PM
Modified
Sep 28, 2026, 5:17 PM
Severity
Important
Public date
Sep 26, 2026, 1:23 PM