CVE-2025-627187.0HighCWE-918

CVE-2025-62718: Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF

axios

Vendor fix available · Affected: axios · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.2%probability of exploitation in the next 30 days

68th percentile

050100

Higher than 68% of scored CVEs

7.0HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

axios · axios>= 1.0.0, < 1.15.0; < 0.31.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Server-Side Request Forgery
Vendor: axios
Published: April 2026
Band: Possible (1 to 10%), April 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2025-62718 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

28 more references are in the CVE record.