{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-62243 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-62243 is a high-severity vulnerability in netty, published on 22 Aug 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-62243 and fix it if it is affected.\n\nWhat it is: CVE-2026-62243 is a high-severity vulnerability in netty, published on 22 Aug 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-62243 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-62243/ (Markdown: https://insights.sbomify.com/CVE-2026-62243/index.md)","id":"CVE-2026-62243","markdown":"https://insights.sbomify.com/CVE-2026-62243/index.md","name":"CVE-2026-62243","record":{"aliases":["CLEANSTART-2026-CP08538","CLEANSTART-2026-EA97597","CLEANSTART-2026-EX11941","CLEANSTART-2026-GU46395","CLEANSTART-2026-KB58666","CLEANSTART-2026-PH97070","DEBIAN-CVE-2026-62243","GHSA-c3j3-64rf-grvf","GHSA-p85m-gvr3-788c","UBUNTU-CVE-2026-62243"],"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":"Man-in-the-middle attackers can bypass TLS hostname verification in Netty under specific Java 25+ configurations, accepting invalid certificates.","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-297","name":"Improper Validation of Certificate with Host Mismatch"}],"description":"Netty (io.netty:netty-handler) versions from 4.2.0.Final through 4.2.16.Final and versions through 4.1.136.Final disable TLS hostname verification on the SslProvider.OPENSSL client path when a plain (non-extended) X509TrustManager is used and Unsafe-based trust-manager wrapping is unavailable (Java 25+). In this configuration the OpenSSL client does not perform hostname verification, allowing a man-in-the-middle attacker to present a certificate issued for a different hostname that is accepted without validation. Fixed in 4.2.17.Final and 4.1.137.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":true,"headline":"Netty 4.2.0 through 4.2.16 TLS Hostname Verification Bypass","id":"CVE-2026-62243","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":"Missing authorization in kamaji","id":"CVE-2026-62246"},"packages":[],"prev":{"headline":"Spring Boot Admin Server \u003c 4.1.2 SSRF via Unauthenticated Instance Registration","id":"CVE-2026-62242"},"products":["netty"],"published":"2026-08-22","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-08-24","vendors":["netty"]},"summary":"Man-in-the-middle attackers can bypass TLS hostname verification in Netty under specific Java 25+ configurations, accepting invalid certificates.","url":"https://insights.sbomify.com/CVE-2026-62243/"}