GHSA-cmxv-58fp-fm3g
MEDIUMGHSA-cmxv-58fp-fm3g is a medium-severity (CVSS 6.8) Information Exposure vulnerability in org.asynchttpclient:async-http-client. O3 Security confirms whether GHSA-cmxv-58fp-fm3g is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
AsyncHttpClient leaks authorization credentials to untrusted domains on cross-origin redirects
Blast Radius
org.asynchttpclient:async-http-client☕org.asynchttpclient:async-http-clientReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
When redirect following is enabled (followRedirect(true)), AsyncHttpClient forwards Authorization and Proxy-Authorization headers along with Realm credentials to arbitrary redirect targets regardless of domain, scheme, or port changes. This leaks credentials on cross-domain redirects and HTTPS-to-HTTP downgrades.
Additionally, even when stripAuthorizationOnRedirect is set to true, the Realm object containing plaintext credentials is still propagated to the redirect request, causing credential re-generation for Basic and Digest authentication schemes via NettyRequestFactory.
An attacker who controls a redirect target (via open redirect, DNS rebinding, or MITM on HTTP) can capture Bearer tokens, Basic auth credentials, or any other Authorization header value.
Patches
Fixed in version 3.0.9 or 2.14.5. Users should upgrade immediately.
The fix automatically strips Authorization and Proxy-Authorization headers and clears Realm credentials whenever a redirect crosses origin boundaries (different scheme, host, or port) or downgrades from HTTPS to HTTP.
Workarounds
For users unable to upgrade, set (stripAuthorizationOnRedirect(true)) in the client config and avoid using Realm-based authentication with redirect following enabled. Note that (stripAuthorizationOnRedirect(true)) alone is insufficient on versions prior to 3.0.9 or 2.14.5 because the Realm bypass still re-generates credentials.
Alternatively, disable redirect following (followRedirect(false)) and handle redirects manually with origin validation.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.asynchttpclient:async-http-client | ≥ 3.0.0.Beta1&&< 3.0.9 | 3.0.9 |
| ☕Maven | org.asynchttpclient:async-http-client | ≥ 2.0.0&&< 2.14.5 | 2.14.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.asynchttpclient:async-http-client. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.asynchttpclient:async-http-client to 3.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cmxv-58fp-fm3g is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-cmxv-58fp-fm3g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-cmxv-58fp-fm3g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-cmxv-58fp-fm3g in your dependencies?
O3 detects GHSA-cmxv-58fp-fm3g across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.