Skip to content
Fencer Intel
medium 5.9

CVE-2026-107285 json

AsyncHttpClient: WebSocket proxy credentials sent to the origin server over a CONNECT tunnel

published last mo. modified last mo. also EUVD-2026-94645 , GHSA-3wp9-xfwm-rjjf

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits
0
none known

Summary

The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. Prior to 3.0.12 and 2.16.1, a proxied ws request is carried through CONNECT, but NettyRequestFactory.newNettyRequest and requestUri decide whether to attach proxy authentication and an absolute-form target only from whether the URI is secure. Because ws is not marked secure, the tunneled WebSocket upgrade sent to the origin includes the proxy's Proxy-Authorization value. Basic credentials are directly recoverable and Digest responses can be replayed or cracked offline. This issue is fixed in versions 3.0.12 and 2.16.1.

Patch / fix

  • maven org.asynchttpclient:async-http-client 2.16.1, 3.0.12
  • asynchttpclient_project async-http-client 2.16.1, 3.0.12
  • org.asynchttpclient async-http-client 2.16.1, 3.0.12

Is CVE-2026-107285 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-107285 updated cvss 5.9

org.asynchttpclient/async-http-client: async-http-client: Information disclosure via proxy credential leak in WebSocket requests

  • Red Hat Fuse 7 async-http-client 2.0.40
    affected: workaround, no fix planned “Out of support scope”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.asynchttpclient:async-http-client
>=3.0.0, <3.0.12
>=2.0.0, <2.16.1
3.0.12
2.16.1

Affected products

  • AsyncHttpClient async-http-client

Classification

Weakness
  • CWE-319 Cleartext Transmission of Sensitive Information
  • CWE-522 Insufficiently Protected Credentials

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.