{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-85719 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-85719 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85719 is a high-severity 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-85719 and fix it if it is affected.\n\nWhat it is: CVE-2026-85719 is a high-severity 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-85719 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-85719/ (Markdown: https://insights.sbomify.com/CVE-2026-85719/index.md)","id":"CVE-2026-85719","markdown":"https://insights.sbomify.com/CVE-2026-85719/index.md","name":"CVE-2026-85719","record":{"aliases":["DEBIAN-CVE-2026-85719","GHSA-x5w6-vm3f-pp6f","UBUNTU-CVE-2026-85719"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Java HTTP client library","requires_auth":"none","summary":"AsyncHttpClient leaks SOCKS proxy credentials to origin servers via plaintext HTTP or malicious 407 responses, exposing sensitive authentication data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 2.16.1 and 3.0.12, requests using an authenticated SOCKS proxy can expose the proxy's credentials to the origin because NettyRequestFactory and NettyRequestSender attach Proxy-Authorization without confirming that the request is being sent to an HTTP proxy. With preemptive proxy authentication, the header is attached to a plaintext HTTP request, exposing credentials such as directly reversible Basic credentials to the origin. With the default non-preemptive flow, a hostile origin can return a 407 response and ProxyUnauthorized407Interceptor sends the proxy credentials through the existing SOCKS tunnel, including NTLM, Kerberos, and SPNEGO credentials. Releases before 2.1.0 lack SOCKS proxy support. This issue is fixed in versions 2.16.1 and 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: SOCKS proxy credentials sent to the origin server over plaintext HTTP","id":"CVE-2026-85719","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"AsyncHttpClient: Origin credentials sent to the proxy on the plaintext CONNECT request","id":"CVE-2026-85720"},"packages":[],"prev":{"headline":"AsyncHttpClient: Connection permit leak on TLS handshake failure causes per-host denial of service","id":"CVE-2026-85718"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["AsyncHttpClient"]},"summary":"AsyncHttpClient leaks SOCKS proxy credentials to origin servers via plaintext HTTP or malicious 407 responses, exposing sensitive authentication data.","url":"https://insights.sbomify.com/CVE-2026-85719/"}