AsyncHttpClient (AHC) contains a credential forwarding flaw when redirect following is enabled via followRedirect(true). In versions prior to 3.0.9 and 2.14.5, the library forwards Authorization and Proxy-Authorization headers, as well as Realm-backed credentials, to redirect targets even when the redirect changes origin boundaries such as scheme, host, or port, including HTTPS-to-HTTP downgrades. The issue also affects configurations using stripAuthorizationOnRedirect(true): although headers may be stripped, the Realm object containing plaintext credentials is still propagated to the redirected request, allowing NettyRequestFactory to regenerate Basic or Digest authentication credentials for the new target. As a result, credentials intended for one origin can be disclosed to arbitrary redirect destinations controlled by an attacker.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.