axios: Unintended Proxy or Intermediary
CVE-2025-62718 is a critical-severity unintended proxy or intermediary vulnerability in axios, with a CVSS 3.1 base score of 9.9 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected axios versions: >= 1.0.0, < 1.15.0; < 0.31.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.21% chance of exploitation within 30 days, higher than 69% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of axios you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 6.3 | Medium | CNA (github.com) |
| CVSS 3.1 | 9.9 | Critical | NVD |
| CVSS 3.1 | 7.0 | High | CNA |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Unintended Proxy or Intermediary
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.
How developers prevent this class of flaw
- Enforce the use of strong mutual authentication mechanism between the two parties.
- Whenever a product is an intermediary or proxy for transactions between two other components, the proxy core should not drop the identity of the initiator of the transaction. The immutability of the identity of the initiator must be maintained and should be forwarded all the way to the target.
More Unintended Proxy or Intermediary vulnerabilities (CWE-441)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/axios/axios/security/advisories/GHSA-3p68-rc4w-qgx5Exploit, Mitigation
Patches and release notes
- github.com/axios/axios/commit/03cdfc99e8db32a390e12128208b6778492cee9c
- github.com/axios/axios/commit/fb3befb6daac6cad26b2e54094d0f2d9e47f24df
- github.com/axios/axios/pull/10661Issue Tracking
- github.com/axios/axios/pull/10688Issue Tracking
- github.com/axios/axios/releases/tag/v0.31.0Release Notes
- github.com/axios/axios/releases/tag/v1.15.0Product, Release Notes
Other references
- datatracker.ietf.org/doc/html/rfc1034#section-3.1Technical Description
- datatracker.ietf.org/doc/html/rfc3986#section-3.2.2Technical Description
- access.redhat.com/errata/RHSA-2026:10175
- access.redhat.com/errata/RHSA-2026:13571
- access.redhat.com/errata/RHSA-2026:13826
- access.redhat.com/errata/RHSA-2026:14937
- access.redhat.com/errata/RHSA-2026:16874
- access.redhat.com/errata/RHSA-2026:17657
- access.redhat.com/errata/RHSA-2026:17699
- access.redhat.com/errata/RHSA-2026:19375
- access.redhat.com/errata/RHSA-2026:19712
- access.redhat.com/errata/RHSA-2026:20889
- access.redhat.com/errata/RHSA-2026:20938
- access.redhat.com/errata/RHSA-2026:21017
- access.redhat.com/errata/RHSA-2026:22465
Other vulnerabilities in axios
- 8.3 High severity
- 7.0 High severity
- 8.2 High severity
- 7.6 High severity
- 8.2 High severity
- 8.2 High severity
Recent Unintended Proxy or Intermediary vulnerabilities
- 9.1 Critical severity
- 8.4 High severity
- 8.4 High severity
- 8.4 High severity
- 8.4 High severity
- 7.8 High severity
Spotted an error? Tell us.