Quick answers
- Is CVE-2026-44492 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44492 being exploited in the wild.
- How severe is CVE-2026-44492?
- High severity, with a CVSS score of 8.6, published 11 June 2026.
- Which products and versions are affected?
- Axios >= 1.0.0, < 1.16.0; <= 0.31.1; axios (npm) SEMVER:introduced=1.15.0,fixed=1.16.0.
- Is there a fix for CVE-2026-44492?
- 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-44492 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44492?
- 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 Server-Side Request Forgery (SSRF) vulnerability exists in Axios due to improper normalization of IPv4-mapped IPv6 addresses in the 'shouldBypassProxy' helper. When a 'NO_PROXY' list contains an IPv4 address (e.g., 127.0.0.1), an attacker can provide a URL using the equivalent IPv6-mapped format (e.g., ::ffff:7f00:1). Because Axios does not recognize these as identical, it routes the request through the configured proxy instead of bypassing it. Node.js then resolves these addresses to the underlying IPv4 host, allowing the request to reach internal services or cloud metadata endpoints (IMDS). This is an incomplete fix for a previous vulnerability and is resolved in versions 0.32.0 and 1.16.0.
Affected products
- Axios Axios >= 1.0.0, < 1.16.0; < 0.32.0
Identifiers
- CVE-2026-44492
- GHSA-pjwm-pj3p-43mv
Timeline
- 2026-05-29: advisory: GitHub advisory published by maintainers
- 2026-06-11: disclosed: CVE-2026-44492 published to NVD