{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100665 exists.","fix":"No fix has been published for CVE-2026-100665 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100665 is a high-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-100665 and fix it if it is affected.\n\nWhat it is: CVE-2026-100665 is a high-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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100665 exists.\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-100665/ (Markdown: https://insights.sbomify.com/CVE-2026-100665/index.md)","id":"CVE-2026-100665","markdown":"https://insights.sbomify.com/CVE-2026-100665/index.md","name":"CVE-2026-100665","record":{"aliases":["GHSA-4qw4-fmqv-qhv8","GHSA-mj35-3qqm-q387","UBUNTU-CVE-2026-100665"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Java networking library","requires_auth":"none","summary":"Attackers can bypass QUIC hostname verification in Netty when using plain trust managers, allowing man-in-the-middle attacks against clients configured for HTTPS verification.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Netty versions from 4.2.11.Final before 4.2.18.Final contain an incomplete hostname verification fix in the QUIC certificate verification path when using a plain X509TrustManager. The BoringSSLCertificateVerifyCallback discards the SSLEngine for plain trust managers, preventing endpoint identification from running even when HTTPS verification is configured. Attackers on the network path can present a certificate chain for the wrong hostname that the plain trust manager accepts, bypassing hostname authentication for QUIC clients.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Netty 4.2.11 through 4.2.17 QUIC Hostname Verification Bypass","id":"CVE-2026-100665","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Netty 4.2.0 through 4.2.16 Response Desynchronization via HttpServerCodec","id":"CVE-2026-100666"},"packages":[],"prev":{"headline":"Netty 4.2.2 through 4.2.17 HTTP/1 Host Header Authority Confusion","id":"CVE-2026-100664"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-02","vendors":["netty"]},"summary":"Attackers can bypass QUIC hostname verification in Netty when using plain trust managers, allowing man-in-the-middle attacks against clients configured for HTTPS verification.","url":"https://insights.sbomify.com/CVE-2026-100665/"}