UBUNTU-CVE-2026-100664 (CVE-2026-100664)
Vulnerability from osv_ubuntu – Published: 2026-09-26 14:16 – Updated: 2026-09-30 21:41 – Source website
VLAI
Details
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.
Severity
7.5 (High)
N/A (UNKNOWN)
References
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnetty-java",
"binary_version": "1:3.2.6.Final-2+deb8u2ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "netty",
"purl": "pkg:deb/ubuntu/netty@1:3.2.6.Final-2+deb8u2ubuntu0.1~esm1?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1:3.2.6.Final-2",
"1:3.2.6.Final-2+deb8u2build0.14.04.1~esm1",
"1:3.2.6.Final-2+deb8u2ubuntu0.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnetty-java",
"binary_version": "1:4.0.34-1ubuntu0.1~esm5"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "netty",
"purl": "pkg:deb/ubuntu/netty@1:4.0.34-1ubuntu0.1~esm5?arch=source\u0026distro=esm-apps-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1:3.2.6.Final-2",
"1:4.0.32-1",
"1:4.0.33-1",
"1:4.0.34-1",
"1:4.0.34-1ubuntu0.1~esm1",
"1:4.0.34-1ubuntu0.1~esm2",
"1:4.0.34-1ubuntu0.1~esm3",
"1:4.0.34-1ubuntu0.1~esm4",
"1:4.0.34-1ubuntu0.1~esm5"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnetty-java",
"binary_version": "1:4.1.7-4ubuntu0.1+esm7"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "netty",
"purl": "pkg:deb/ubuntu/netty@1:4.1.7-4ubuntu0.1+esm7?arch=source\u0026distro=esm-apps/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1:4.1.7-4",
"1:4.1.7-4ubuntu0.1~esm1",
"1:4.1.7-4ubuntu0.1",
"1:4.1.7-4ubuntu0.1+esm1",
"1:4.1.7-4ubuntu0.1+esm2",
"1:4.1.7-4ubuntu0.1+esm3",
"1:4.1.7-4ubuntu0.1+esm4",
"1:4.1.7-4ubuntu0.1+esm5",
"1:4.1.7-4ubuntu0.1+esm6",
"1:4.1.7-4ubuntu0.1+esm7"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnetty-java",
"binary_version": "1:4.1.45-1ubuntu0.1~esm7"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "netty",
"purl": "pkg:deb/ubuntu/netty@1:4.1.45-1ubuntu0.1~esm7?arch=source\u0026distro=esm-apps/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1:4.1.33-1",
"1:4.1.33-2",
"1:4.1.33-3",
"1:4.1.45-1",
"1:4.1.45-1ubuntu0.1~esm1",
"1:4.1.45-1ubuntu0.1~esm2",
"1:4.1.45-1ubuntu0.1~esm3",
"1:4.1.45-1ubuntu0.1~esm4",
"1:4.1.45-1ubuntu0.1~esm6",
"1:4.1.45-1ubuntu0.1~esm7"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnetty-java",
"binary_version": "1:4.1.48-4+deb11u2ubuntu0.2+esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:22.04:LTS",
"name": "netty",
"purl": "pkg:deb/ubuntu/netty@1:4.1.48-4+deb11u2ubuntu0.2+esm1?arch=source\u0026distro=esm-apps/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1:4.1.48-4",
"1:4.1.48-4+deb11u1build0.22.04.1",
"1:4.1.48-4+deb11u2build0.22.04.1",
"1:4.1.48-4+deb11u2ubuntu0.1~esm1",
"1:4.1.48-4+deb11u2ubuntu0.1~esm2",
"1:4.1.48-4+deb11u2ubuntu0.1",
"1:4.1.48-4+deb11u2ubuntu0.1+esm1",
"1:4.1.48-4+deb11u2ubuntu0.1+esm3",
"1:4.1.48-4+deb11u2ubuntu0.2",
"1:4.1.48-4+deb11u2ubuntu0.2+esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnetty-java",
"binary_version": "1:4.1.48-9ubuntu0.2+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:24.04:LTS",
"name": "netty",
"purl": "pkg:deb/ubuntu/netty@1:4.1.48-9ubuntu0.2+esm2?arch=source\u0026distro=esm-apps/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1:4.1.48-7",
"1:4.1.48-8",
"1:4.1.48-9",
"1:4.1.48-9ubuntu0.1~esm1",
"1:4.1.48-9ubuntu0.1~esm2",
"1:4.1.48-9ubuntu0.1",
"1:4.1.48-9ubuntu0.1+esm1",
"1:4.1.48-9ubuntu0.1+esm3",
"1:4.1.48-9ubuntu0.2",
"1:4.1.48-9ubuntu0.2+esm1",
"1:4.1.48-9ubuntu0.2+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnetty-buffer-java",
"binary_version": "1:4.1.48-16ubuntu0.1~esm2"
},
{
"binary_name": "libnetty-common-java",
"binary_version": "1:4.1.48-16ubuntu0.1~esm2"
},
{
"binary_name": "libnetty-java",
"binary_version": "1:4.1.48-16ubuntu0.1~esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:26.04:LTS",
"name": "netty",
"purl": "pkg:deb/ubuntu/netty@1:4.1.48-16ubuntu0.1~esm2?arch=source\u0026distro=esm-apps/resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1:4.1.48-10",
"1:4.1.48-11",
"1:4.1.48-12",
"1:4.1.48-13",
"1:4.1.48-14",
"1:4.1.48-16",
"1:4.1.48-16ubuntu0.1~esm2"
]
}
],
"aliases": [],
"details": "Netty\u0027s 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) \u2014 reached via Http3FrameToHttpObjectCodec(false) \u2014 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.",
"id": "UBUNTU-CVE-2026-100664",
"modified": "2026-09-30T21:41:52Z",
"published": "2026-09-26T14:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-100664"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-100664"
},
{
"type": "REPORT",
"url": "https://github.com/netty/netty/security/advisories/GHSA-hfr2-x62w-v49h"
},
{
"type": "REPORT",
"url": "https://www.vulncheck.com/advisories/netty-4.2.2-through-4.2.15-http-1-host-header-authority-confusion"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "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",
"type": "CVSS_V4"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-100664"
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…