All vulnerabilities

npm

CVE-2026-101898

Axios: HTTP/2 adapter bypasses configured DNS lookup and proxy controls

Severity
High
Published
30 Sept 2026
Last changed
30 Sept 2026
Added to UpHeron
22 Oct 2026
Fixed in
1.20.0
Exploit chance
0.5% in the next 30 daysHigher than 46% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Server-side request forgery (CWE-918)
Also known as
GHSA-3pq3-5fj3-cg6v
Sources
OSV.dev and GitHub

Description

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.

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.

From the GitHub Advisory Database, CC BY 4.0. Shortened; the full text is there.

Workarounds

Use the HTTP/1 adapter path for requests that depend on axios lookup or proxy controls. Alternatively, enforce destination allow/deny policy before calling axios, outside the adapter transport path.

Original report

Workarounds as given by the GitHub Advisory Database, CC BY 4.0.

Affected software

SoftwareAffected versions
axiosnpm · osv:npm:axios
  • From 1.13.0 before 1.20.0

About axios

Weekly downloads (npm)
143,624,637npm, 16 Nov 2026

References