SSRF (Server-Side Request Forgery) in axios (CVE-2026-101898)
Summary
SSRF in axios (CVE-2026-101898). Risk of unauthorized operations or information disclosure. Exploitable via config.lookup. Mitigation: upgrade to 1.20.0 or later.
Original description
The description as published by the source.
Summary
Axios for Node.js does not apply configured DNS lookup or proxy controls when a request uses httpVersion: 2. The HTTP/1 adapter path wraps and forwards config.lookup, builds normal request options, and applies proxy routing through setProxy(). The HTTP/2 path builds a session with http2.connect() using only options.http2Options, which drops the top-level lookup, agent, and proxy state.
Applications are affected when they allow a user to influence request destinations, enable axios HTTP/2, and rely on axios lookup or proxy routing to prevent SSRF or enforce outbound network policy.
Impact
In affected server-side deployments, an attacker can cause axios to connect directly to destinations that the configured resolver or proxy would have rejected. Depending on reachable services, this can expose cloud metadata, internal service responses, or allow state-changing requests to internal systems.
This is not an unconditional SSRF in every axios deployment. It requires httpVersion: 2 and an application-level trust boundary where user-influenced URLs are constrained by lookup or proxy policy.
Affected Functionality
Affected:
- Node.js HTTP adapter with
httpVersion: 2. config.lookupsupplied as a DNS policy.- Explicit
config.proxyand environment-derived proxy settings for HTTPS HTTP/2 requests.
Not affected:
- Browser adapters.
- Node HTTP/1 requests, which pass
lookupto the transport and apply proxy handling. - Applications th…
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-101898 has been found in axios.
Attackers can target a specific entry point like config.lookup over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade axios to 1.20.0 or later.
If unsure, ask your IT team or search "axios CVE-2026-101898" on the vendor's site.
CVE-2026-101898 (axios) — CWE-918
Attack surface: config.lookup / options.http2Options / lookup / agent
Patched: 1.20.0 — apply immediately
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.
SSRF (CWE-918) exists in axios. Attackers reach the vulnerable code path via config.lookup.
Check the vendor advisory for the affected versions of axios. Attack surface: config.lookup / options.http2Options / lookup / agent.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.20.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade axios to 1.20.0ステージング環境で 1.20.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com