CVE-2026-100666
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 22% of all known CVEs.
References
Related Vulnerabilities
Other CWE-444 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-22536 | Critical | 10.0 | 98% | KEV | - |
| CVE-2025-61884 | High | 7.5 | 96% | KEV + Ransom | - |
| CVE-2020-9490 | High | 7.5 | 89% | - | Fix |
| CVE-2023-41265 | Critical | 9.6 | 88% | KEV + Ransom | - |
| CVE-2023-25690 | Critical | 9.8 | 85% | - | Fix |
| CVE-2022-32214 | Medium | 6.5 | 82% | - | Fix |
Common questions
How do I fix CVE-2026-100666?
No published fix for CVE-2026-100666 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-100666 being actively exploited?
Not that we know of. CVE-2026-100666 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.29% is the estimated probability that it will be exploited in the next 30 days. That is higher than 22% of all scored CVEs.
How severe is CVE-2026-100666?
CVE-2026-100666 has a CVSS v3 base score of 7.3, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-100666
Markdown
[](https://tridentstack.com/cve/CVE-2026-100666)HTML
<a href="https://tridentstack.com/cve/CVE-2026-100666"><img src="https://tridentstack.com/cve/badge/CVE-2026-100666.svg" alt="CVE-2026-100666"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-30.