Axios v1.15.0 Proxy Bypass via NO_PROXY Handling SSRF
CVE-2025-62718 Published on April 9, 2026
Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.0 and 0.31.0, Axios does not correctly handle hostname normalization when checking NO_PROXY rules. Requests to loopback addresses like localhost. (with a trailing dot) or [::1] (IPv6 literal) skip NO_PROXY matching and go through the configured proxy. This goes against what developers expect and lets attackers force requests through a proxy, even if NO_PROXY is set up to protect loopback or internal services. This issue leads to the possibility of proxy bypass and SSRF vulnerabilities allowing attackers to reach sensitive loopback or internal services despite the configured protections. This vulnerability is fixed in 1.15.0 and 0.31.0.
Vulnerability Analysis
CVE-2025-62718 is exploitable with network access, and does not require authorization privileges or user interaction. This vulnerability is consided to have a high level of attack complexity. An automatable proof of concept (POC) exploit exists. The potential impact of an exploit of this vulnerability is considered to have a high impact on confidentiality, with no impact on integrity and availability.
Weakness Types
What is a Confused Deputy Vulnerability?
The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.
CVE-2025-62718 has been classified to as a Confused Deputy vulnerability or weakness.
What is a SSRF Vulnerability?
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.
CVE-2025-62718 has been classified to as a SSRF vulnerability or weakness.
Improper Validation of Unsafe Equivalence in Input
The product receives an input value that is used as a resource identifier or other type of reference, but it does not validate or incorrectly validates that the input is equivalent to a potentially-unsafe value.
Products Associated with CVE-2025-62718
You can be notified by email with stack.watch whenever vulnerabilities like CVE-2025-62718 are published in these products:
Affected Versions
axios:- Version >= 1.0.0, < 1.15.0 is affected.
- Version < 0.31.0 is affected.
- Version 0:2.5.20260422-3.el8ap and below * is unaffected.
- Version 0:2.5.20260422-3.el9ap and below * is unaffected.
- Version 1781116645 and below * is unaffected.
- Version 1781116658 and below * is unaffected.
- Version 1781116387 and below * is unaffected.
- Version 1781116392 and below * is unaffected.
- Version 1781116667 and below * is unaffected.
- Version 1778511348 and below * is unaffected.
- Version 1778383863 and below * is unaffected.
- Version 1778508956 and below * is unaffected.
- Version 1778510461 and below * is unaffected.
- Version 1783451729 and below * is unaffected.
- Version 1779371594 and below * is unaffected.
- Version 1779293013 and below * is unaffected.
- Version 1780082949 and below * is unaffected.
- Version 1779784904 and below * is unaffected.
- Version 1776784286 and below * is unaffected.
- Version 1777903262 and below * is unaffected.
- Version 1778156756 and below * is unaffected.
- Version 1783690532 and below * is unaffected.
- Version 1780467029 and below * is unaffected.
- Version 1780467147 and below * is unaffected.
- Version 1779189627 and below * is unaffected.
- Version 1778473763 and below * is unaffected.
- Version 1778666987 and below * is unaffected.
- Version 1776744110 and below * is unaffected.
- Version 1776795511 and below * is unaffected.
- Version 1776202125 and below * is unaffected.
- Version 1776191302 and below * is unaffected.
- Version 1776151124 and below * is unaffected.
- Version 1776151272 and below * is unaffected.
- Version 1776151106 and below * is unaffected.
- Version 1776151270 and below * is unaffected.
- Version 1776155669 and below * is unaffected.
- Version 1776149682 and below * is unaffected.
- Version 1776151134 and below * is unaffected.
- Version 1776151277 and below * is unaffected.
- Version 1779822261 and below * is unaffected.
- Version 1779811412 and below * is unaffected.
- Version 1779689392 and below * is unaffected.
- Version 1780891395 and below * is unaffected.
- Version 1779204086 and below * is unaffected.
- Version 1779922205 and below * is unaffected.
- Version 1779811473 and below * is unaffected.
- Version 1779971506 and below * is unaffected.
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.