{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-85718 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-85718 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85718 is a medium-severity denial of service vulnerability in AsyncHttpClient async-http-client, published on 17 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-85718 and fix it if it is affected.\n\nWhat it is: CVE-2026-85718 is a medium-severity denial of service vulnerability in AsyncHttpClient async-http-client, published on 17 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-85718 in the wild and no public exploit code.\n\nAffected product: AsyncHttpClient async-http-client. 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-85718/ (Markdown: https://insights.sbomify.com/CVE-2026-85718/index.md)","id":"CVE-2026-85718","markdown":"https://insights.sbomify.com/CVE-2026-85718/index.md","name":"CVE-2026-85718","record":{"aliases":["GHSA-gcmv-gr82-6m8v","UBUNTU-CVE-2026-85718"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Java HTTP client library","requires_auth":"none","summary":"Attackers can cause per-host denial of service in AsyncHttpClient by triggering TLS handshake failures, leaking connection permits when limits are configured.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-772","name":"Missing Release of Resource after Effective Lifetime"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 3.0.8 until 3.0.12, a client with maxConnections or maxConnectionsPerHost set above zero leaks one connection permit whenever TLS connection establishment fails before the handshake completes. NettyConnectListener removes the partitionKeyLock permit from NettyResponseFuture before every failure path is bound to the channel closeFuture, so an abort can leave the permit unreleased. Repeated failures can permanently lock out one host under a per-host limit or drain the shared pool under a global limit, blocking later requests even when no connection remains open. The default unlimited connection setting is not affected. This issue is fixed in version 3.0.12.","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":"AsyncHttpClient: Connection permit leak on TLS handshake failure causes per-host denial of service","id":"CVE-2026-85718","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"AsyncHttpClient: SOCKS proxy credentials sent to the origin server over plaintext HTTP","id":"CVE-2026-85719"},"packages":[],"prev":{"headline":"AsyncHttpClient: Client-wide realm credentials re-sent to a cross-origin redirect target","id":"CVE-2026-85717"},"products":["async-http-client"],"published":"2026-09-17","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["AsyncHttpClient"]},"summary":"Attackers can cause per-host denial of service in AsyncHttpClient by triggering TLS handshake failures, leaking connection permits when limits are configured.","url":"https://insights.sbomify.com/CVE-2026-85718/"}