CVE-2026-107285: AsyncHttpClient WebSocket Proxy Credentials Sent To Vulnerability

MODERATE
Advisory Identifier: GHSA-3wp9-xfwm-rjjf
CVSS 5.9
CWE-319 CWE-522
Published
Advisory Summary

CVE-2026-107285 is a MODERATE (CVSS 5.9) websocket proxy credentials sent to vulnerability (CWE-319: Cleartext Transmission of Sensitive Information) affecting AsyncHttpClient libraries in the Maven ecosystem. The issue involves websocket proxy credentials sent to the origin server over a connect tunnel. Remediation is available by upgrading affected packages to version 3.0.12, 2.16.1.

CVE-2026-107285 at a Glance

CVE Identifier CVE-2026-107285
GHSA Identifier GHSA-3wp9-xfwm-rjjf
Severity MODERATE
CVSS v3.1 Base Score 5.9
CWE Classification CWE-319: Cleartext Transmission of Sensitive Information
Affected Product AsyncHttpClient
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-107285

To remediate this vulnerability, upgrade all affected AsyncHttpClient dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.asynchttpclient:async-http-client fixed: 3.0.12
<dependency>
    <groupId>org.asynchttpclient</groupId>
    <artifactId>async-http-client</artifactId>
    <version>3.0.12</version>
</dependency>
org.asynchttpclient:async-http-client fixed: 2.16.1
<dependency>
    <groupId>org.asynchttpclient</groupId>
    <artifactId>async-http-client</artifactId>
    <version>2.16.1</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.asynchttpclient

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-107285, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.asynchttpclient

Analyze the terminal output to locate any version of AsyncHttpClient in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.12), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.asynchttpclient command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-319: Cleartext Transmission of Sensitive Information, where the product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. In AsyncHttpClient, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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. The preemptive Proxy-Authorization header and the absolute-form request target are no longer attached to a tunnelled ws:// upgrade; a ws:// request is now treated like wss://. ### Workarounds Do not use proxy authentication together with ws:// requests through an HTTP proxy, or use wss:// instead. ### Details The proxy-auth gate in NettyRequestFactory#newNettyRequest and the sibling branch in requestUri() did not exclude WebSocket URIs, even though the CONNECT-tunnelling check in NettyRequestSender already tunnels ws:// through CONNECT exactly like https://. Note that 3.0.12 is itself affected by a separate issue, GHSA-rqf5-2wxv-rjf4, where a Digest challenge the client cannot read downgrades to Basic and sends the password in cleartext. Upgrade to 3.0.13 to pick up both fixes.

CVE-2026-107285 Affected AsyncHttpClient Versions

2 component(s)
Fixed Versions:
3.0.122.16.1
Product / Package Ecosystem Affected Versions Fixed Version
org.asynchttpclient:async-http-client
Maven
≥ 3.0.0
< 3.0.12
3.0.12
org.asynchttpclient:async-http-client
Maven
≥ 2.0.0
< 2.16.1
2.16.1

References

Frequently Asked Questions

What is CVE-2026-107285?
CVE-2026-107285 is a security vulnerability in AsyncHttpClient involving WebSocket proxy credentials sent to the origin server over a CONNECT tunnel under CWE-319: Cleartext Transmission of Sensitive Information.
Which AsyncHttpClient versions are affected?
Affected versions include releases prior to 3.0.12, 2.16.1 across affected packages: org.asynchttpclient:async-http-client.
What version fixes CVE-2026-107285?
Upgrading to 3.0.12, 2.16.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is async-http-client affected?
Yes, org.asynchttpclient:async-http-client is affected in releases prior to 3.0.12, 2.16.1. Upgrade your dependency to 3.0.12, 2.16.1 or later.
What is the CVSS score of CVE-2026-107285?
CVE-2026-107285 has a CVSS v3.1 base score of 5.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-107285?
CVE-2026-107285 is classified under CWE-319: Cleartext Transmission of Sensitive Information (The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.).
How can I check Maven dependencies for CVE-2026-107285?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.asynchttpclient'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3wp9-xfwm-rjjf",
  "modified" : "2026-10-08T16:30:58Z",
  "published" : "2026-10-08T16:30:58Z",
  "aliases" : [ "CVE-2026-107285" ],
  "summary" : "AsyncHttpClient: WebSocket proxy credentials sent to the origin server over a CONNECT tunnel",
  "details" : "### Impact\nWhen 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.\n\n### Affected versions\n* 3.x: up to and including 3.0.11\n* 2.x: up to and including 2.16.0\n\n### Patches\nFixed in 3.0.12 on the 3.x line and in 2.16.1 on the 2.x line. The preemptive Proxy-Authorization header and the absolute-form request target are no longer attached to a tunnelled ws:// upgrade; a ws:// request is now treated like wss://.\n\n### Workarounds\nDo not use proxy authentication together with ws:// requests through an HTTP proxy, or use wss:// instead.\n\n### Details\nThe proxy-auth gate in NettyRequestFactory#newNettyRequest and the sibling branch in requestUri() did not exclude WebSocket URIs, even though the CONNECT-tunnelling check in NettyRequestSender already tunnels ws:// through CONNECT exactly like https://.\n\nNote that 3.0.12 is itself affected by a separate issue, GHSA-rqf5-2wxv-rjf4, where a Digest challenge the client cannot read downgrades to Basic and sends the password in cleartext. Upgrade to 3.0.13 to pick up both fixes.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.asynchttpclient:async-http-client"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.0.12"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.0.11"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.asynchttpclient:async-http-client"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.16.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.16.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-3wp9-xfwm-rjjf"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-107285"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/AsyncHttpClient/async-http-client/commit/6e9cb75a9b7259353f983fc90ca28b1da3742e18"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/AsyncHttpClient/async-http-client/commit/c4feab0f7f86d61505a48e40d383c8a375a22e18"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/AsyncHttpClient/async-http-client"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-2.16.1"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-3.0.12"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-319", "CWE-522" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-08T16:30:58Z",
    "nvd_published_at" : "2026-10-07T22:17:04Z"
  }
}