Quick answers
- Is CVE-2026-44486 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44486 being exploited in the wild.
- How severe is CVE-2026-44486?
- High severity, with a CVSS score of 7.5, published 11 June 2026.
- Which products and versions are affected?
- Axios >= 1.0.0, <= 1.15.0; < 0.32.0; axios (npm) SEMVER:introduced=1.0.0,fixed=1.16.0.
- Is there a fix for CVE-2026-44486?
- Yes. axios (npm): upgrade to 1.16.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44486 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44486?
- Check whether you run Axios or axios (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- axios (npm): upgrade to 1.16.0 or later
npm install axios@1.16.0
Technical details
A vulnerability exists in the Axios Node.js HTTP adapter (lib/adapters/http.js) where the 'Proxy-Authorization' header is not cleared during request redirects. When an initial request is made through an authenticated proxy, the 'setProxy()' function attaches the authorization header. If the request is redirected to a target that resolves to a direct connection (e.g., via NO_PROXY or a missing HTTPS_PROXY setting), Axios re-evaluates the proxy settings but fails to remove the existing header. An attacker-controlled server can trigger a redirect to capture these credentials. This issue is fixed in versions 0.32.0 and 1.16.0.
Affected products
- Axios Axios >= 1.0.0, <= 1.15.0; < 0.32.0
Identifiers
- CVE-2026-44486
- GHSA-j5f8-grm9-p9fc
Timeline
- 2026-05-30: advisory: GitHub Security Advisory published
- 2026-06-11: disclosed: CVE published to NVD