{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-100659 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-100659 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100659 is a medium-severity vulnerability in netty, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-100659 and fix it if it is affected.\n\nWhat it is: CVE-2026-100659 is a medium-severity vulnerability in netty, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-100659 in the wild and no public exploit code.\n\nAffected product: netty. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-100659/ (Markdown: https://insights.sbomify.com/CVE-2026-100659/index.md)","id":"CVE-2026-100659","markdown":"https://insights.sbomify.com/CVE-2026-100659/index.md","name":"CVE-2026-100659","record":{"aliases":["GHSA-7j27-hw46-m8m8","GHSA-q9pg-8h3j-8hvm","UBUNTU-CVE-2026-100659"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java networking library","requires_auth":"none","summary":"Remote attackers can bypass routing and access controls in Netty HTTP/3 by sending conflicting authority headers, affecting applications using the library.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"Netty's HTTP/3 codec (io.netty:netty-codec-http3) in versions 4.2.0.Final through 4.2.17.Final does not enforce the RFC 9114 requirement that the :authority pseudo-header field and a literal host header field, when both present, carry the same value. A remote unauthenticated peer can send a single HEADERS frame containing both fields with differing, attacker-controlled values; the request is accepted and delivered to the application with two conflicting authorities, allowing routing, virtual-host, and access-control decisions to be bypassed when different components in the request path consult different fields. This issue is fixed in 4.2.18.Final.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Netty 4.2.0 through 4.2.17 HTTP/3 Request Routing Bypass","id":"CVE-2026-100659","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Netty before 4.2.18.Final QpackEncoder Unbounded Memory Retention","id":"CVE-2026-100660"},"packages":[],"prev":{"headline":"This CVE ID has been rejected as a duplicate.","id":"CVE-2026-100658"},"products":["netty"],"published":"2026-09-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["netty"]},"summary":"Remote attackers can bypass routing and access controls in Netty HTTP/3 by sending conflicting authority headers, affecting applications using the library.","url":"https://insights.sbomify.com/CVE-2026-100659/"}