Vulnerability in axios (CVE-2026-67315)
Summary
Vulnerability in axios (CVE-2026-67315). Confidential information can be exposed externally. Exploitable via NO_PROXY. Mitigation: upgrade to 0.33.0 or later.
Original description
The description as published by the source.
axios versions 0.31.0 before 0.33.0 and 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 NO_PROXY rules. Attackers can supply 0.0.0.0 URLs to route requests through configured proxies, potentially exposing local services when the proxy can reach the destination.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-67315 has been found in axios.
Attackers can target a specific entry point like NO_PROXY over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade axios to 0.33.0 or later.
If unsure, ask your IT team or search "axios CVE-2026-67315" on the vendor's site.
CVE-2026-67315 (axios) — CWE-183 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: NO_PROXY / HTTP_PROXY / HTTPS_PROXY / localhost
Patched: 0.33.0 — apply immediately
Workaround: set proxy: false
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-183) exists in axios. Attackers reach the vulnerable code path via NO_PROXY without authentication.
Check the vendor advisory for the affected versions of axios. Attack surface: NO_PROXY / HTTP_PROXY / HTTPS_PROXY / localhost.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 0.33.0.
Workaround: set proxy: false
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'axios' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'axios' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
axiosを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
set proxy: falseパッチが適用されるまでの応急処置として、set proxy: false を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade axios to 0.33.0ステージング環境で 0.33.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-67315 node-axios Fixed in: 1.18.0-1
- Ubuntu UBUNTU-CVE-2026-67315 node-axios
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com