dbcve.org
AxiosApplication

CVE-2026-44492

HIGH · 8.6 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 0.32.0 / 1.16.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, Axios does not normalise IPv4-mapped IPv6 addresses. When NO_PROXY lists an IPv4 address such as 127.0.0.1 or 169.254.169.254, a request URL using the IPv4-mapped IPv6 form (::ffff:7f00:1, ::ffff:a9fe:a9fe) still routes through the configured proxy. Node.js resolves these addresses to the underlying IPv4 host, so the request reaches the internal service via the proxy rather than being blocked. This vulnerability is fixed in 0.32.0 and 1.16.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Axios prior to 0.32.0 and 1.16.0 does not normalize IPv4-mapped IPv6 addresses when checking the NO_PROXY environment variable. When NO_PROXY contains an IPv4 address like 127.0.0.1 or 169.254.169.254, requests using the IPv6-mapped form (::ffff:7f00:1 or ::ffff:a9fe:a9fe) bypass NO_PROXY and route through the configured proxy instead of being blocked. This allows attackers to bypass proxy-based access controls to reach internal services.

MitigationUpgrade Axios to version 0.32.0, 1.16.0, or later to include the IPv6 address normalization fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AxiosApplication
Affected:< 0.32.0>= 1.0.0, < 1.16.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Axios version
    Run `npm list axios` or inspect package.json to find the axios version
    Affected if version is less than 0.32.0, or greater than or equal to 1.0.0 but less than 1.16.0
  2. Verify NO_PROXY configuration exists
    Inspect environment variables NO_PROXY or no_proxy, or Axios config options for NO_PROXY. Look for IPv4 addresses like 127.0.0.1 or 169.254.169.254
    Affected if NO_PROXY contains private or loopback IPv4 addresses and Axios version is vulnerable
  3. Identify requests to IPv6-mapped addresses
    Review application code or network logs for requests using IPv6-mapped IPv4 syntax such as ::ffff:127.0.0.1, ::ffff:169.254.169.254, or ::1 with port forwarding to internal services
    Affected if application makes requests to IPv6-mapped forms of addresses that are listed in NO_PROXY as IPv4
  4. Confirm proxy is being bypassed
    Compare request routing: if a request to an IPv6-mapped address (like ::ffff:169.254.169.254) goes through the proxy while the same address as IPv4 (169.254.169.254) respects NO_PROXY, the vulnerability is present
    Affected if IPv6-mapped addresses bypass NO_PROXY and route through proxy while equivalent IPv4 addresses correctly bypass proxy

You are affected if you use a vulnerable Axios version with NO_PROXY rules containing IPv4 addresses and your application makes requests using IPv6-mapped address syntax.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.32.0 / 1.16.0 or later
Fixed in 0.32.01.16.0
Interim mitigation

Upgrade Axios to version 0.32.0, 1.16.0, or later to include the IPv6 address normalization fix.

Recommended fix High confidence

0.32.0 or 1.16.0 (or later stable releases)

  1. Upgrade Axios to version 0.32.0 or higher if using the 0.x major version branch
  2. Upgrade Axios to version 1.16.0 or higher if using the 1.x major version branch
  3. After upgrading, verify that NO_PROXY settings correctly block IPv4-mapped IPv6 address variants (e.g., ::ffff:127.0.0.1, ::ffff:169.254.169.254)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Axios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44492 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44492 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data