Description
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.
Recommendation
Update the axios package to the latest compatible version. Followings are version details:
Affected version(s): **< 0.31.0 >= 1.0.0, < 1.15.0** Patched version(s): **0.31.0 1.15.0**
References
Could your website be exposed too?
SmartScanner can check your website for Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF and gives you actionable findings to investigate.
Start a free scanRelated Issues
- Axios: Incomplete Fix for CVE-2025-62718 — NO_PROXY Protection Bypassed via RFC 1122 Loopback Subnet (127.0.0.0/8) in Ax - CVE-2026-42043
- @octokit/request has a Regular Expression in fetchWrapper that Leads to ReDoS Vulnerability Due to Catastrophic Backtrac - CVE-2025-25290
- Axios has a Patch Bypass: Proxy-Authorization Header Injection via Prototype Pollution — Incomplete Null-Prototype Fix - CVE-2026-44489
- OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header that leads to cross‑tenant data ex - CVE-2026-30956
You might also like:
See something that needs correcting? Let us knowUpdated April 16, 2026