axios versions 1.15.0 before 1.18.0 fail to recognize 0.0.0.0 as a loopback address in shouldBypassProxy.js, allowing requests to 0.0.0.0 to bypass… (CVE-2026-67315)
Axios versions from 1.15.0 up to but not including 1.18.0 contain a vulnerability where the IP address 0.0.0.0 is not recognized as a loopback address in the shouldBypassProxy.js component. This causes requests to 0.0.0.0 to bypass NO_PROXY rules, potentially routing these requests through configured proxies. This behavior can expose local services if the proxy has access to the destination address.
AI Analysis
Technical Summary
The vulnerability in axios versions 1.15.0 before 1.18.0 arises from a failure to identify 0.0.0.0 as a loopback address within the shouldBypassProxy.js logic. As a result, requests targeting 0.0.0.0 do not bypass proxy settings as intended by NO_PROXY environment variables. Attackers can exploit this by supplying URLs with 0.0.0.0, causing requests to be routed through proxies that may have network access to internal or local services, potentially exposing those services unintentionally.
Potential Impact
Requests to 0.0.0.0 can bypass NO_PROXY rules and be routed through proxies, which may expose local or internal services accessible by the proxy. This could lead to unintended information disclosure or access to internal resources if the proxy is trusted and can reach those destinations.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch is available, users should avoid using axios versions 1.15.0 through 1.17.x with untrusted proxy configurations or consider implementing additional proxy bypass checks externally to mitigate this issue.
axios versions 1.15.0 before 1.18.0 fail to recognize 0.0.0.0 as a loopback address in shouldBypassProxy.js, allowing requests to 0.0.0.0 to bypass… (CVE-2026-67315)
Description
Axios versions from 1.15.0 up to but not including 1.18.0 contain a vulnerability where the IP address 0.0.0.0 is not recognized as a loopback address in the shouldBypassProxy.js component. This causes requests to 0.0.0.0 to bypass NO_PROXY rules, potentially routing these requests through configured proxies. This behavior can expose local services if the proxy has access to the destination address.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in axios versions 1.15.0 before 1.18.0 arises from a failure to identify 0.0.0.0 as a loopback address within the shouldBypassProxy.js logic. As a result, requests targeting 0.0.0.0 do not bypass proxy settings as intended by NO_PROXY environment variables. Attackers can exploit this by supplying URLs with 0.0.0.0, causing requests to be routed through proxies that may have network access to internal or local services, potentially exposing those services unintentionally.
Potential Impact
Requests to 0.0.0.0 can bypass NO_PROXY rules and be routed through proxies, which may expose local or internal services accessible by the proxy. This could lead to unintended information disclosure or access to internal resources if the proxy is trusted and can reach those destinations.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch is available, users should avoid using axios versions 1.15.0 through 1.17.x with untrusted proxy configurations or consider implementing additional proxy bypass checks externally to mitigate this issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6hqm-hm2v-3p2p
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-67315"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a6e6294bf32cb7a344f6952
Added to database: 08/01/2026, 21:18:12 UTC
Last enriched: 08/01/2026, 21:22:14 UTC
Last updated: 08/01/2026, 22:17:49 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.