PatchSiren cyber security CVE debrief
CVE-2026-85719 AsyncHttpClient CVE debrief
The AsyncHttpClient library in Java applications allows easy execution of HTTP requests and asynchronous processing of HTTP responses. A vulnerability exists from versions 2.1.0 to 2.16.1 and 3.0.12, where requests using an authenticated SOCKS proxy can expose the proxy's credentials to the origin server due to improper handling of Proxy-Authorization headers.
- Vendor
- AsyncHttpClient
- Product
- async-http-client
- CVSS
- HIGH 7.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-17
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-17
- Advisory updated
- 2026-09-18
Who should care
Defenders and security teams responsible for Java applications using the AsyncHttpClient library should assess exposure and prioritize remediation to prevent SOCKS proxy credential exposure.
Why it matters
CVE-2026-85719 exposes SOCKS proxy credentials in AsyncHttpClient library. Defenders should verify exposure, prioritize remediation, and upgrade to fixed versions to prevent credential misuse.
- Potential exposure of sensitive SOCKS proxy credentials
- Risk of credential misuse by malicious actors
- Need for verification of affected versions and exposure in applications
- Priority on upgrading to fixed AsyncHttpClient library versions
Technical summary
The AsyncHttpClient library in Java applications has a vulnerability (CVE-2026-85719) where requests using an authenticated SOCKS proxy can expose the proxy's credentials to the origin server. This occurs due to improper handling of Proxy-Authorization headers in NettyRequestFactory and NettyRequestSender. Affected versions are from 2.1.0 to 2.16.1 and 3.0.12. Fixed versions are 2.16.1 and 3.0.12.
Defensive priority
Defenders should prioritize verifying exposure of SOCKS proxy credentials and upgrading to fixed versions (2.16.1 or 3.0.12) to prevent credential exposure.
Recommended defensive actions
- Verify if applications using AsyncHttpClient library are exposed to SOCKS proxy credential risks
- Upgrade to AsyncHttpClient library version 2.16.1 or 3.0.12
- Review and adjust SOCKS proxy configurations to prevent credential exposure
- Monitor for potential misuse of exposed credentials
- Perform vulnerability scanning to identify exposed systems
- Implement additional logging and monitoring for SOCKS proxy usage
- Review and update incident response plans to address potential credential exposure
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including affected versions and fixed releases. GitHub commits and security advisories offer additional context on the patches and potential impact.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-85719 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-85719
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-85719 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-85719
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/AsyncHttpClient/async-http-client/commit/4d887704dec22027310f66c81503226722e9bd23
-
Source reference
Unverified legacy reference
URL: https://github.com/AsyncHttpClient/async-http-client/commit/718ed2e86126663a88ea3db7a88cbbf93f0069b5
-
Source reference
Unverified legacy reference
URL: https://github.com/AsyncHttpClient/async-http-client/commit/abaa8bd260beda3b85825ff95069ed11eaf4ca8d
-
Source reference
Unverified legacy reference
URL: https://github.com/AsyncHttpClient/async-http-client/commit/be439b2ec773d12d61914c238d3e8eeaa6f0ba21
-
Source reference
Unverified legacy reference
URL: https://github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-x5w6-vm3f-pp6f
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.