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-101899 Overview
CVE-2026-101899 is a protection mechanism failure [CWE-693] in Axios, a promise-based HTTP client for the browser and Node.js. Versions 1.15.0 through 1.19.x incorrectly evaluate NO_PROXY entries specified in Classless Inter-Domain Routing (CIDR) notation. The shouldBypassProxy function treats CIDR values as textual hostname suffixes rather than evaluating them as network ranges. Requests destined for addresses inside a NO_PROXY CIDR range are routed through the configured proxy instead of bypassing it. For plaintext HTTP traffic, the proxy can observe and modify URLs, headers, and bodies. For HTTPS traffic, the proxy can observe connection metadata and CONNECT requests. The issue is fixed in Axios 1.20.0.
Critical Impact
Internal traffic intended to bypass corporate proxies is unexpectedly routed through them, exposing request contents and metadata to proxy operators.
Affected Products
- Axios 1.15.0 through 1.19.x (Node.js HTTP client)
- Applications relying on NO_PROXY CIDR entries to exclude internal networks from proxying
- Server-side Node.js services that configure proxies alongside CIDR-based NO_PROXY rules
Discovery Timeline
- 2026-10-13 - CVE-2026-101899 published to the National Vulnerability Database (NVD)
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2026-101899
Vulnerability Analysis
Axios reads the NO_PROXY environment variable to determine which destinations should bypass a configured HTTP or HTTPS proxy. The shouldBypassProxy helper iterates each NO_PROXY entry and compares it to the request host. Entries supplied in CIDR notation such as 10.0.0.0/8 are compared as string suffixes rather than parsed as network ranges. A request to 10.1.2.3 is checked against the literal string 10.0.0.0/8, which fails. The request is then sent through the configured proxy. The resulting behavior violates the operator's intent to keep internal traffic off the proxy path and can expose sensitive internal API calls to an intermediary.
Root Cause
The root cause is missing CIDR parsing in the NO_PROXY matcher. The implementation treats every NO_PROXY entry as a hostname or hostname suffix. It does not detect the / prefix length separator or convert addresses and prefix lengths into integer ranges for comparison. This maps to [CWE-693] Protection Mechanism Failure because a configured security control, the proxy bypass list, silently fails for a documented input format.
Attack Vector
An operator or attacker who controls a proxy that an Axios client is configured to use can observe traffic that was supposed to bypass that proxy. For plaintext HTTP, the proxy sees full request URLs, headers, cookies, and bodies, and can tamper with responses. For HTTPS, the proxy observes CONNECT targets and TLS metadata. No exploit code is required because misrouting occurs automatically whenever a NO_PROXY CIDR entry is configured.
// Patch excerpt from lib/core/Axios.js — hardened runtime option handling
// Source: https://github.com/axios/axios/commit/d19040bda7a8be2f82c3c6e1a5bc03917daee39a
// Set config.method
config.method = (
utils.getSafeProp(config, 'method') ||
utils.getSafeProp(this.defaults, 'method') ||
'get'
).toLowerCase();
// Flatten headers
let contextHeaders = headers && utils.merge(headers.common, headers[config.method]);
headers &&
utils.forEach(
['delete', 'get', 'head', 'post', 'put', 'patch', 'query', 'common'],
(method) => {
delete headers[method];
}
);
config.headers = AxiosHeaders.concat(contextHeaders, headers);
The companion change in lib/adapters/fetch.js introduces a DEFAULT_REQUEST_OPTIONS object that pins safe defaults for cache, redirect, referrer, mode, integrity, keepalive, and priority. See the GitHub Security Advisory GHSA-44g4-m2mj-wpvx and Pull Request #11141 for the full change set.
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-101899
Indicators of Compromise
- Outbound proxy logs containing CONNECT or GET requests whose destination addresses fall inside internal CIDR ranges listed in NO_PROXY.
- Node.js services running Axios versions 1.15.0 through 1.19.x with a HTTP_PROXY or HTTPS_PROXY plus CIDR entries in NO_PROXY.
- Unexpected TLS handshakes between application servers and the forward proxy for internal-only hostnames.
Detection Strategies
- Inventory package-lock.json and yarn.lock files for Axios versions in the vulnerable range using Software Composition Analysis (SCA) tooling.
- Compare NO_PROXY configuration against actual proxy access logs to identify traffic that should have bypassed the proxy.
- Flag container images and build artifacts that pin Axios to >=1.15.0 <1.20.0 as part of CI/CD policy gates.
Monitoring Recommendations
- Enable verbose logging on forward proxies and alert on destination IPs matching RFC1918 ranges that were declared in NO_PROXY.
- Monitor Node.js process environment variables at runtime to confirm NO_PROXY entries use expected formats.
- Track upgrades of the axios dependency across all services until every instance reports version 1.20.0 or later.
How to Mitigate CVE-2026-101899
Immediate Actions Required
- Upgrade Axios to version 1.20.0 or later in all Node.js services and browser bundles.
- Audit forward proxy logs for internal traffic that was unintentionally proxied while running affected versions.
- Rotate any credentials, tokens, or session cookies that may have transited the proxy in plaintext HTTP requests.
Patch Information
The fix is included in Axios v1.20.0 via commit d19040bd and Pull Request #11141. The release corrects NO_PROXY CIDR evaluation and hardens runtime option handling in both the fetch adapter and the core request pipeline.
Workarounds
- Replace CIDR entries in NO_PROXY with explicit hostnames or IP addresses that match the string-suffix logic of affected Axios versions.
- Set proxy: false on individual Axios request configurations that target internal hosts to force a direct connection.
- Terminate internal traffic through a separate HTTP client that correctly interprets NO_PROXY CIDR entries until the upgrade is complete.
# Upgrade Axios to the patched release
npm install axios@^1.20.0
# Verify installed version
npm ls axios
# Temporary workaround: expand CIDR into explicit host entries
export NO_PROXY="localhost,127.0.0.1,10.1.2.3,10.1.2.4,internal.example.com"
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

