Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.0amended

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

CVE-2026-101898GHSA-3pq3-5fj3-cg6v

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (axios 1.20.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm axios

    Affected
    >= 1.13.0, < 1.20.0
    Fixed in
    1.20.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.0 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N · score source
EPSS
  • CVE-2026-101898: 0.55% estimated exploitation activity in the next 30 days; percentile 45.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-3pq3-5fj3-cg6v

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-3pq3-5fj3-cg6v

  4. Revision 1 · created ·

    Published from ghsa record GHSA-3pq3-5fj3-cg6v

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-101898

Advisory: Axios: HTTP/2 adapter bypasses configured DNS lookup and proxy controls
IDs: CVE-2026-101898, GHSA-3pq3-5fj3-cg6v
Record: https://patchnext.com/advisories/cve-2026-101898 (revision 4, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: axios 1.20.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm axios: affected >= 1.13.0, < 1.20.0; fixed in 1.20.0

## Suggested inspection (read-only)
- `npm ls axios --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on axios.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3pq3-5fj3-cg6v (GitHub-reviewed advisory GHSA-3pq3-5fj3-cg6v lists affected ranges: npm axios >=1.13.0 <1.20.0)
- Verified: https://osv.dev/vulnerability/GHSA-3pq3-5fj3-cg6v (OSV record GHSA-3pq3-5fj3-cg6v lists affected ranges: npm axios >=1.13.0 <1.20.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…