Netty's HttpServerCodec (io.netty:netty-codec-http) in versions 4.2.0.Final through 4.2.16.Final and in versions up to and including 4.1.136.Final pairs each outbound response with an inbound request by calling pollMethod() once per response, including for 1xx informational responses. If a client pipelines an HTTP/1.1 GET carrying an Expect: 100-continue header followed by a HEAD request, the 100 Continue response consumes the queued GET method, so the subsequent 200 OK for the GET is paired with HEAD and its body is dropped, while the following 200 OK for the HEAD request is written with a body. This desynchronizes HTTP parsing on the connection: the GET entity is never delivered and the HEAD response body is interpreted as the GET body, resulting in response splitting and unsafe connection reuse. Fixed in 4.2.17.Final and 4.1.137.Final.
Netty 4.2.0 through 4.2.17 Response Desynchronization via HttpServerCodec
Problem type
Affected products
netty
< 4.2.17.Final - AFFECTED
4.2.17.Final - UNAFFECTED
< 4.1.137.Final - AFFECTED
4.1.137.Final - UNAFFECTED
References
https://github.com/netty/netty/security/advisories/GHSA-2g6j-r8q9-5hr8
https://www.vulncheck.com/advisories/netty-4.2.0-through-4.2.17-response-desynchronization-via-httpservercodec
GitHub Security Advisories
GHSA-jq5g-c66v-g3r2
Netty's HttpServerCodec (io.netty:netty-codec-http) in versions 4.2.0.Final through 4.2.16.Final...
https://github.com/advisories/GHSA-jq5g-c66v-g3r2Netty's HttpServerCodec (io.netty:netty-codec-http) in versions 4.2.0.Final through 4.2.16.Final and in versions up to and including 4.1.136.Final pairs each outbound response with an inbound request by calling pollMethod() once per response, including for 1xx informational responses. If a client pipelines an HTTP/1.1 GET carrying an Expect: 100-continue header followed by a HEAD request, the 100 Continue response consumes the queued GET method, so the subsequent 200 OK for the GET is paired with HEAD and its body is dropped, while the following 200 OK for the HEAD request is written with a body. This desynchronizes HTTP parsing on the connection: the GET entity is never delivered and the HEAD response body is interpreted as the GET body, resulting in response splitting and unsafe connection reuse. Fixed in 4.2.17.Final and 4.1.137.Final.
https://github.com/netty/netty/security/advisories/GHSA-2g6j-r8q9-5hr8
https://nvd.nist.gov/vuln/detail/CVE-2026-100666
https://www.vulncheck.com/advisories/netty-4.2.0-through-4.2.17-response-desynchronization-via-httpservercodec
https://github.com/advisories/GHSA-jq5g-c66v-g3r2
JSON source
https://cveawg.mitre.org/api/cve/CVE-2026-100666Click to expand
{
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"cveMetadata": {
"cveId": "CVE-2026-100666",
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"dateUpdated": "2026-09-26T13:23:31.961Z",
"dateReserved": "2026-09-26T02:34:55.634Z",
"datePublished": "2026-09-26T13:23:31.961Z",
"state": "PUBLISHED"
},
"containers": {
"cna": {
"providerMetadata": {
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck",
"dateUpdated": "2026-09-26T13:23:31.961Z"
},
"datePublic": "2026-09-10T00:00:00.000Z",
"title": "Netty 4.2.0 through 4.2.17 Response Desynchronization via HttpServerCodec",
"descriptions": [
{
"lang": "en",
"value": "Netty's HttpServerCodec (io.netty:netty-codec-http) in versions 4.2.0.Final through 4.2.16.Final and in versions up to and including 4.1.136.Final pairs each outbound response with an inbound request by calling pollMethod() once per response, including for 1xx informational responses. If a client pipelines an HTTP/1.1 GET carrying an Expect: 100-continue header followed by a HEAD request, the 100 Continue response consumes the queued GET method, so the subsequent 200 OK for the GET is paired with HEAD and its body is dropped, while the following 200 OK for the HEAD request is written with a body. This desynchronizes HTTP parsing on the connection: the GET entity is never delivered and the HEAD response body is interpreted as the GET body, resulting in response splitting and unsafe connection reuse. Fixed in 4.2.17.Final and 4.1.137.Final."
}
],
"affected": [
{
"vendor": "netty",
"product": "netty",
"defaultStatus": "unaffected",
"versions": [
{
"version": "4.2.0.Final",
"status": "affected",
"versionType": "semver",
"lessThan": "4.2.17.Final"
},
{
"version": "4.2.17.Final",
"status": "unaffected",
"versionType": "semver"
}
]
},
{
"vendor": "netty",
"product": "netty",
"defaultStatus": "unaffected",
"versions": [
{
"version": "0",
"status": "affected",
"versionType": "semver",
"lessThan": "4.1.137.Final"
},
{
"version": "4.1.137.Final",
"status": "unaffected",
"versionType": "semver"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"lang": "en",
"description": "Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')",
"cweId": "CWE-444",
"type": "CWE"
}
]
}
],
"references": [
{
"url": "https://github.com/netty/netty/security/advisories/GHSA-2g6j-r8q9-5hr8",
"name": "GitHub Security Advisory (GHSA-2g6j-r8q9-5hr8)",
"tags": [
"vendor-advisory"
]
},
{
"url": "https://www.vulncheck.com/advisories/netty-4.2.0-through-4.2.17-response-desynchronization-via-httpservercodec",
"name": "VulnCheck Advisory: Netty 4.2.0 through 4.2.17 Response Desynchronization via HttpServerCodec",
"tags": [
"third-party-advisory"
]
}
],
"metrics": [
{
"format": "CVSS"
},
{
"format": "CVSS",
"cvssV3_1": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
"attackVector": "NETWORK",
"attackComplexity": "LOW",
"privilegesRequired": "NONE",
"userInteraction": "NONE",
"scope": "UNCHANGED",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"availabilityImpact": "LOW",
"baseScore": 7.3,
"baseSeverity": "HIGH"
}
}
],
"credits": [
{
"lang": "en",
"value": "violetagg",
"type": "reporter"
}
]
}
}
}