CVE-2026-101898: Axios: HTTP/2 adapter bypasses configured DNS lookup and proxy controls
Axios is a promise-based HTTP client for the browser and Node.js. From 1.13.0 until 1.20.0, Axios HTTP/2 request setup does not consistently apply proxy settings and caller-supplied DNS lookup policy. An HTTPS request uses httpVersion: 2 with explicit config.proxy or environment-derived proxy settings, or relies on caller-supplied config.lookup DNS policy. The HTTP/2 path can connect without the configured proxy behavior or without applying the caller-supplied config.lookup policy before http2.connect(). Requests can bypass the intended proxy route or the caller-supplied DNS resolution policy. This issue is fixed in version 1.20.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
axiosto a version that resolves this vulnerability.Fixed in 1.20.0
Event History
Frequently Asked Questions
Which applications are exposed to this issue?
Applications using Axios versions 1.13.0 through 1.19.x are affected when they make HTTPS requests with httpVersion: 2 and rely on explicit or environment-derived proxy settings, or on a caller-supplied config.lookup DNS policy.
What must an attacker be able to influence for this to matter?
The vulnerable request flow must be used to access an attacker-influenced or otherwise untrusted HTTPS destination. The impact is that the connection may avoid the intended proxy route or caller-provided DNS-resolution restrictions.
Are default Axios configurations affected?
The issue depends on HTTP/2 being selected with httpVersion: 2 and on use of proxy configuration or a caller-supplied config.lookup policy. The provided information does not indicate that ordinary requests without those settings are affected.
What should teams do if they use these controls?
Upgrade Axios to version 1.20.0. Until then, avoid relying on the affected HTTP/2 path to enforce proxy routing or caller-supplied DNS lookup policy.