AsyncHttpClient: WebSocket proxy credentials sent to the origin server over a CONNECT tunnel
CVE-2026-107285GHSA-3wp9-xfwm-rjjf
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.asynchttpclient:async-http-client 3.0.12, 2.16.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.asynchttpclient:async-http-client
- Affected
- >= 3.0.0, <= 3.0.11>= 2.0.0, <= 2.16.0
- Fixed in
- 2.16.1, 3.0.12
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-3wp9-xfwm-rjjf lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.0.0 <2.16.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-3wp9-xfwm-rjjf lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.0.0 <=2.16.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-107285: 0.21% estimated exploitation activity in the next 30 days; percentile 10.67 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact When a ws:// request is routed through an HTTP proxy with proxy authentication configured, the client tunnels the connection with an HTTP CONNECT, the same as it does for https://. Once the tunnel is open, the WebSocket upgrade request that follows is sent through the tunnel directly to the origin server, not to the proxy. The proxy-auth gate and the companion request-target selection keyed only on whether the URI was secured, which is false for ws://, so the tunnelled upgrade request incorrectly carried the proxy's Proxy-Authorization header and an absolute-form request target meant for the proxy. Any origin server reached over a proxied ws:// connection, or anyone positioned on the origin side of the wire, could recover the proxy credentials: directly for Basic, or as a replayable and offline-crackable response for Digest. Affected versions 3.x: up to and including 3.0.11 2.x: up to and including 2.16.0 Patches Fixed in 3.0.12 on the 3.x line and in 2.16.1 on the 2.x line.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-3wp9-xfwm-rjjf
- Revision 1 · created ·
Published from osv record GHSA-3wp9-xfwm-rjjf
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-107285 Advisory: AsyncHttpClient: WebSocket proxy credentials sent to the origin server over a CONNECT tunnel IDs: CVE-2026-107285, GHSA-3wp9-xfwm-rjjf Record: https://patchnext.com/advisories/cve-2026-107285 (revision 2, source checked 26 Oct 2026, 16:58 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.asynchttpclient:async-http-client 3.0.12, 2.16.1. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.asynchttpclient:async-http-client: affected >= 3.0.0, <= 3.0.11; >= 2.0.0, <= 2.16.0; fixed in 2.16.1, 3.0.12 ## Suggested inspection (read-only) - Maven org.asynchttpclient:async-http-client: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.asynchttpclient:async-http-client. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-3wp9-xfwm-rjjf (OSV record GHSA-3wp9-xfwm-rjjf lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.0.0 <2.16.1 (fixed)) - Verified: https://github.com/advisories/GHSA-3wp9-xfwm-rjjf (GitHub-reviewed advisory GHSA-3wp9-xfwm-rjjf lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.0.0 <=2.16.0) Commands are suggestions: review each one before running it.
Loading voting…