Quick answers
- Is CVE-2026-44489 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44489 being exploited in the wild.
- How severe is CVE-2026-44489?
- Low severity, with a CVSS score of 3.7, published 29 May 2026.
- Which products and versions are affected?
- Axios 1.15.2 to < 1.16.0; axios (npm) SEMVER:introduced=1.15.2,fixed=1.16.0.
- Is there a fix for CVE-2026-44489?
- 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-44489 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44489?
- 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
This vulnerability is a bypass of the fix for GHSA-q8qp-cvcw-x6jj. While the top-level configuration object in Axios 1.15.2 uses a null prototype, nested objects created via 'utils.merge()' (such as 'config.proxy') are still initialized as plain JavaScript objects. These objects inherit from 'Object.prototype', making them vulnerable to prototype pollution. The 'setProxy()' function in 'lib/adapters/http.js' reads properties like 'username' and 'password' without 'hasOwnProperty' checks. If an attacker pollutes 'Object.prototype.username', Axios will automatically construct and inject a 'Proxy-Authorization' header into all proxied requests. This requires a pre-existing prototype pollution vulnerability in the application's dependency tree and the explicit use of a proxy configuration. The issue is fixed in version 1.16.0.
Affected products
- Axios Axios 1.15.2 to < 1.16.0
Identifiers
- CVE-2026-44489
- GHSA-654m-c8p4-x5fp
Timeline
- 2026-05-29: advisory: GitHub advisory published
- 2026-06-11: disclosed: NVD publication date
- 2026-06-11: patched: Fixed in version 1.16.0