CVE-2026-85720: AsyncHttpClient: Origin credentials sent to the proxy on the plaintext CONNECT request
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: org.asynchttpclient:async-http-client (Maven) 2.16.1, 3.0.12.
Low priority for now. Upgrade to org.asynchttpclient:async-http-client (Maven) 2.16.1, 3.0.12 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.0.0 until 2.16.1 and 3.0.12, a request using an HTTP proxy to reach an HTTPS origin can expose preemptive origin credentials because NettyRequestFactory and NettyRequestSender.sendRequestWithNewChannel attach Authorization to the plaintext CONNECT request before the TLS tunnel exists. Basic or Digest credentials and per-connection NTLM, Kerberos, or SPNEGO tokens intended for the origin are therefore visible to the proxy and to observers on the client-to-proxy hop. The tunneled request still receives origin Authorization after the tunnel is established, while Proxy-Authorization remains on CONNECT for its intended proxy recipient. This issue is fixed in versions 2.16.1 and 3.0.12.
- Published
- Sep 17, 2026
- Updated
- Sep 24, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- CWE-319
Report tools
Action score
23
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 5.9
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Check your site's encryptionRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkVersions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
AsyncHttpClient async-http-client
- >= 2.0.0, < 2.16.1, >= 3.0.0, < 3.0.12affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | async-http-client | from 0 | — |
| Maven | org.asynchttpclient:async-http-client | from 2.0.0 · before 2.16.1 | 2.16.1 |
| Maven | org.asynchttpclient:async-http-client | from 3.0.0 · before 3.0.12 | 3.0.12 |
Same product
asynchttpclient: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-107282AsyncHttpClient: Replay to a different host sends the original host request and credentials to the new host37Monitor
- CVE-2024-53990AsyncHttpClient (AHC) library's `CookieStore` replaces explicitly defined `Cookie`s36Monitor
- CVE-2026-107279AsyncHttpClient: Digest mutual authentication is switched off by a peer offering qop=auth-int35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-85719Sep 17, 2026 · AsyncHttpClient: SOCKS proxy credentials sent to the origin server over plaintext HTTP30Monitor
- ← EarlierCVE-2026-85716Sep 17, 2026 · AsyncHttpClient: SCRAM and Digest mutual-authentication responses are not verified14Monitor
- Later →CVE-2026-85717Sep 17, 2026 · AsyncHttpClient: Client-wide realm credentials re-sent to a cross-origin redirect target27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.asynchttpclient:async-http-client | 2.16.1 | Package registry (OSV) |
| Maven:org.asynchttpclient:async-http-client | 3.0.12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-10728220 days apartAsyncHttpClient: Replay to a different host sends the original host request and credentials to the new host37Monitor
- CVE-2026-10723120 days apartAsyncHttpClient: Digest challenge without a usable nonce downgrades to Basic and sends the password in cleartext34Monitor
- CVE-2026-857190 days apartAsyncHttpClient: SOCKS proxy credentials sent to the origin server over plaintext HTTP30Monitor
- CVE-2026-10723220 days apartAsyncHttpClient: Origin credentials sent in cleartext to a proxy that rejects the CONNECT30Monitor
- CVE-2026-10728520 days apartAsyncHttpClient: WebSocket proxy credentials sent to the origin server over a CONNECT tunnel23Monitor
Not on record for this CVE: researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-319 · Cleartext Transmission of Sensitive InformationCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.