dbcve.org
AxiosApplication

CVE-2026-42043

CRITICAL · 10.0 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 0.31.1 / 1.15.1 or later.
See remediation →
100/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 1.15.1 and 0.31.1, an attacker who can influence the target URL of an Axios request can use any address in the 127.0.0.0/8 range (other than 127.0.0.1) to completely bypass the NO_PROXY protection. This vulnerability is due to an incomplete for CVE-2025-62718, This vulnerability is fixed in 1.15.1 and 0.31.1.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 2mo ago

Surfaced from public web coverage — external links open in a new tab.

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

In the NO_PROXY environment variable handling, Axios only excluded 127.0.0.1 from proxy bypass but failed to block the entire 127.0.0.0/8 range (127.0.0.2-127.255.255.255). An attacker who controls the request URL can use addresses like 127.0.0.2 to bypass NO_PROXY protections and access internal services that should have been excluded from proxying.

MitigationUpgrade Axios to version 1.15.1 or 0.31.1, which contains the complete fix for CVE-2025-62718 that now properly handles the full 127.0.0.0/8 loopback range.

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.31.1>= 1.0.0, < 1.15.1

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 installed version of the axios package
    Affected if The installed version is less than 0.31.1, or greater than or equal to 1.0.0 but less than 1.15.1
  2. Identify if NO_PROXY or proxy exclusion is configured
    Search environment variables for NO_PROXY, no_proxy, HTTP_PROXY, HTTPS_PROXY, or check application code for proxy configuration passed to Axios requests (axios.defaults.proxy, request config proxy option)
    Affected if Proxy exclusion rules (NO_PROXY or similar) are configured but only designed to block 127.0.0.1 rather than the full 127.0.0.0/8 range
  3. Verify if application handles user-influenced URLs
    Audit application code to determine whether any endpoint accepts user input that gets incorporated into the URL passed to axios.get(), axios.post(), or similar methods
    Affected if User-controlled or externally-influenced input can construct or modify the request URL
  4. Test loopback range bypass
    If proxy exclusion is configured, make a request to an address like 127.0.0.2, 127.0.1.1, or 127.255.255.254 while ensuring that address is in NO_PROXY, and observe whether the request bypasses the proxy entirely
    Affected if Requests to 127.0.0.2-127.255.255.255 bypass proxy settings while 127.0.0.1 is correctly excluded

You are affected if Axios version is below 1.15.1 (or below 0.31.1 for the 0.x branch), proxy exclusion via NO_PROXY is configured, and user-controlled input can influence request URLs to target the full 127.0.0.0/8 range.

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.31.1 / 1.15.1 or later
Fixed in 0.31.11.15.1
Interim mitigation

Upgrade Axios to version 1.15.1 or 0.31.1, which contains the complete fix for CVE-2025-62718 that now properly handles the full 127.0.0.0/8 loopback range.

Recommended fix High confidence

Axios 1.15.1 (for >=1.0.0) or 0.31.1 (for <1.0.0)

  1. Check the current axios version in package.json (if using version >= 1.0.0, upgrade to 1.15.1; if using version < 1.0.0 like 0.x, upgrade to 0.31.1)
  2. Run `npm install [email protected]` for axios >= 1.0.0, or `npm install [email protected]` for axios 0.x
  3. Alternatively, run `npm install axios@latest` to get the latest stable version which includes the fix
  4. Verify the installation was successful by running `npm list axios`
  5. Test the application to ensure requests and NO_PROXY functionality work as expected
Caveat No breaking changes documented in the provided sources for this security fix

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

Fix this in Axios Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42043 — 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-42043 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