Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-101907 Overview
CVE-2026-101907 is a redirect policy bypass in Axios, a promise-based HTTP client for the browser and Node.js. The vulnerability affects the fetch adapter in versions 1.17.0 through 1.19.x. The adapter ignores the maxRedirects: 0 configuration and follows redirects issued by the server. Applications that rely on this option to block redirect chains lose that guarantee. A redirected request can reach internal endpoints or trigger state-changing operations that the calling code intended to prevent. The issue is categorized under CWE-441: Unintended Proxy or Intermediary and is fixed in Axios 1.20.0.
Critical Impact
Applications using the Axios fetch adapter with maxRedirects: 0 cannot prevent redirect following, exposing internal HTTP endpoints and enabling server-side request forgery style access to unintended resources.
Affected Products
- Axios 1.17.0 through 1.19.x (fetch adapter)
- Node.js applications using Axios with the fetch adapter
- Browser applications using Axios with the fetch adapter
Discovery Timeline
- 2026-09-28 - CVE-2026-101907 published to the National Vulnerability Database
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-101907
Vulnerability Analysis
Axios exposes a maxRedirects configuration option that controls redirect handling on outbound HTTP requests. Setting the value to 0 instructs Axios to return the redirect response unchanged rather than following the Location header. The fetch adapter, introduced in 1.17.0, does not enforce this contract. When a request receives a 3xx status, the underlying fetch implementation transparently follows the redirect. The calling application receives the final response instead of the original redirect. This behavior breaks security controls that depend on redirect suppression, including SSRF protections and allowlists that inspect only the initially-requested host.
Root Cause
The fetch adapter did not translate Axios maxRedirects: 0 into the corresponding redirect: 'manual' option on the underlying fetch() call. Without an explicit override, the fetch runtime defaults to redirect: 'follow'. The patch in Axios 1.20.0 introduces a DEFAULT_REQUEST_OPTIONS object in lib/adapters/fetch.js and hardens runtime option handling to ensure Axios-level configuration is honored.
Attack Vector
An attacker who controls a URL passed to an Axios request, or who controls an upstream service that returns a 3xx response, can redirect the client to an arbitrary destination. Because the adapter follows the redirect despite maxRedirects: 0, the request can reach internal metadata services, loopback endpoints, or state-changing APIs the application intended to shield. The impact is scope-changing: the vulnerable component acts as an unintended intermediary between the attacker and internal systems.
// Patch excerpt from lib/adapters/fetch.js
const DEFAULT_CHUNK_SIZE = 64 * 1024;
const DEFAULT_REQUEST_OPTIONS = {
cache: 'default',
redirect: 'follow',
referrer: 'about:client',
referrerPolicy: '',
mode: 'cors',
integrity: '',
keepalive: false,
priority: 'auto',
window: null,
};
const { isFunction } = utils;
// Source: https://github.com/axios/axios/commit/d19040bda7a8be2f82c3c6e1a5bc03917daee39a
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-101907
Indicators of Compromise
- Outbound HTTP requests from application servers to internal RFC1918 addresses or cloud metadata endpoints such as 169.254.169.254.
- Application logs showing successful responses from URLs different from the originally requested destination.
- Unexpected 3xx responses returned by upstream services followed by requests to sensitive internal hosts.
Detection Strategies
- Inventory application dependencies and flag any project using Axios versions 1.17.0 through 1.19.x via npm ls axios or software composition analysis tooling.
- Review source code for calls that pass maxRedirects: 0 together with the fetch adapter and validate whether SSRF controls depend on that setting.
- Add egress network monitoring to identify HTTP requests that cross security boundaries after a redirect chain.
Monitoring Recommendations
- Instrument HTTP client libraries with request/response logging that captures both the initial URL and the final resolved URL.
- Alert on outbound connections from application tiers to link-local, loopback, or private address ranges.
- Track dependency drift and build failures triggered by pinning Axios to a vulnerable range.
How to Mitigate CVE-2026-101907
Immediate Actions Required
- Upgrade Axios to version 1.20.0 or later across all affected services and rebuild container images.
- Audit code paths that rely on maxRedirects: 0 when using the fetch adapter and confirm redirect behavior post-upgrade.
- Enforce network-level SSRF protections that do not depend solely on client-side redirect settings.
Patch Information
The fix is delivered in Axios release v1.20.0 via pull request #11141 and commit d19040b. Additional context is available in the GitHub Security Advisory GHSA-r4gj-5m52-g5wh.
Workarounds
- Switch to the default http/xhr adapter by removing the explicit adapter: 'fetch' configuration until upgrade is possible.
- Wrap outbound requests with an allowlist that validates the resolved response URL against expected hosts.
- Enforce egress firewall rules that block application traffic to internal address ranges and cloud metadata endpoints.
# Upgrade Axios to the patched release
npm install axios@^1.20.0
# Verify the installed version
npm ls axios
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

