Vulnerability DatabaseCVE-2026-101899

CVE-2026-101899: 
JavaScript vulnerability analysis and mitigation

Overview

CVE-2026-101899 is a proxy exclusion bypass vulnerability in the Axios HTTP client library for Node.js, caused by incorrect handling of CIDR notation in the NO_PROXY environment variable. Affected versions (>=1.15.0, <1.20.0) treat CIDR entries such as 127.0.0.0/8 or 10.0.0.0/8 as literal hostname suffix tokens rather than evaluating them as network ranges, causing requests to addresses within those ranges to be incorrectly routed through the configured proxy. The vulnerability was first published to the GitHub Advisory Database on September 30, 2026, and assigned GHSA-44g4-m2mj-wpvx. It carries a CVSS v3.1 base score of 6.5 (Medium) and a CVSS v4.0 base score of 6.9 (Medium) (Github Advisory, Feedly).

Technical details

The root cause is a logic flaw (CWE-693: Protection Mechanism Failure; CWE-1025: Comparison Using Wrong Factors) in lib/helpers/shouldBypassProxy.js, which parses each NO_PROXY entry into a host and optional port, then performs exact hostname, suffix, wildcard-prefix, and loopback comparisons — but never parses or evaluates CIDR notation. As a result, shouldBypassProxy('http://127.0.0.1:1234/') returns false even when NO_PROXY=127.0.0.0/8 is set, because the CIDR string is silently treated as a non-matching hostname token. Exploitation requires that the target application uses Axios in a Node.js environment with both a proxy configured via HTTP_PROXY/HTTPS_PROXY and CIDR-form entries in NO_PROXY; browser adapters and requests with proxy: false are not affected. A complete, runnable proof-of-concept Node.js script demonstrating the bypass is publicly available in the security advisory (Github Advisory).

Impact

When exploited, a proxy positioned outside the intended trust boundary can observe and modify plaintext HTTP request URLs, headers, and bodies for traffic that operators expected to bypass the proxy entirely. For HTTPS targets, the proxy receives CONNECT requests and observes connection metadata, potentially exposing internal hostnames, paths, and credentials. Environments most at risk include CI/CD runners with globally injected proxy variables, containerized workloads inheriting proxy settings from orchestrators, Kubernetes clusters using CIDR-based NO_PROXY for internal service ranges, and cloud workloads relying on CIDR exclusions to protect metadata endpoints (e.g., 169.254.169.254/32). There is no availability impact, and the vulnerability does not enable arbitrary proxy injection on its own (Github Advisory).

Exploitability

A public proof-of-concept (PoC) Node.js script is available within the official security advisory, demonstrating the CIDR bypass by showing requests routed to a proxy despite CIDR-based NO_PROXY exclusions (Github Advisory). As of the time of reporting, there is no evidence of active in-the-wild exploitation, and no threat actor attribution has been made. The EPSS score is approximately 0.51% (43rd percentile), indicating a low but non-negligible probability of exploitation in the near term. The CVE status is "Awaiting Analysis" and it is not currently listed in the CISA KEV catalog (Feedly).

Exploitation steps

  1. Identify a vulnerable target: Locate a Node.js application using Axios versions >=1.15.0 and <1.20.0 that has both HTTP_PROXY (or HTTPS_PROXY) and NO_PROXY environment variables configured, where NO_PROXY uses CIDR notation (e.g., NO_PROXY=10.0.0.0/8).
  2. Position a proxy: Ensure control over or visibility into the configured proxy server (e.g., a corporate proxy, a compromised intermediary, or an attacker-controlled proxy injected via environment variable manipulation).
  3. Trigger a request to a CIDR-excluded address: Cause the vulnerable application to make an HTTP/HTTPS request to an IP address that falls within the CIDR range specified in NO_PROXY (e.g., a request to http://10.0.1.5/api/internal).
  4. Observe proxy receipt: Because shouldBypassProxy.js does not evaluate the CIDR range, the request is forwarded through the configured proxy instead of going direct. For plaintext HTTP, the proxy receives the full URL, headers, and body; for HTTPS, it receives the CONNECT request and connection metadata.
  5. Extract sensitive data: Inspect the proxy logs or intercept the traffic to harvest internal URLs, authentication headers, API keys, or other sensitive data that was expected to remain off the proxy infrastructure (Github Advisory).

Indicators of compromise

  • Network: Unexpected HTTP CONNECT or plaintext HTTP requests to internal IP ranges (e.g., 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 127.0.0.0/8, 169.254.169.254) appearing in proxy server access logs when those ranges are listed in NO_PROXY.
  • Network: Outbound connections from Node.js application servers to a proxy host for destinations that should be reached directly per CIDR-based exclusion policy.
  • Logs: Proxy access logs showing requests to internal service endpoints, Kubernetes cluster-internal addresses, or cloud metadata endpoints (e.g., 169.254.169.254) that should have bypassed the proxy.
  • Logs: Application-level logs showing successful responses from internal services but with response data originating from the proxy (e.g., response body containing proxy-generated content instead of internal service content).
  • Configuration: Presence of CIDR-form entries in NO_PROXY/no_proxy environment variables alongside HTTP_PROXY/HTTPS_PROXY in Node.js application environments running Axios >=1.15.0 and <1.20.0.

Mitigation and workarounds

Upgrade Axios to version 1.20.0 or later, which adds proper IPv4 and IPv6 CIDR matching to NO_PROXY/no_proxy handling in shouldBypassProxy.js (Axios v1.20.0 Release, Fix PR). As an immediate workaround for environments that cannot upgrade, replace CIDR entries in NO_PROXY with explicit hostnames or individual IP addresses (e.g., NO_PROXY=127.0.0.1,localhost,169.254.169.254). For individual requests that must not traverse a proxy, set proxy: false in the Axios request configuration. Review all deployment environments — particularly CI/CD runners, containers, and Kubernetes workloads — for CIDR-based NO_PROXY configurations and assess exposure (Github Advisory).

Community reactions

The vulnerability was reported by researcher mcdubhghlas and published by Axios maintainer jasonsaayman via the GitHub Security Advisory program. The fix was incorporated into the broader v1.20.0 security hardening release, which also addressed prototype pollution and other runtime consistency issues. Multiple downstream projects — including open-metadata/OpenMetadata, Altinn, chatwoot, and eclipse-che — promptly bumped their Axios dependency to 1.20.0 following the advisory publication, indicating broad community awareness and rapid adoption of the patch (Fix PR).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

node-axios

Fixed

sid

node-axios: 1.20.0-1

Fixed

trixie

node-axios

Fixed

Ubuntu

Unknown

devel

node-axios

Unknown

focal (esm-apps)

node-axios

Unknown

jammy

node-axios

Unknown

jammy (esm-apps)

node-axios

Unknown

noble

node-axios

Unknown

noble (esm-apps)

node-axios

Unknown

resolute

node-axios

Unknown

resolute (esm-apps)

node-axios

Unknown

RHEL / CentOS

Unknown

Source: This report was generated using AI

Related JavaScript vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-133867CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/express
NoYesNov 21, 2026
CVE-2026-133250CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/middie
NoYesNov 21, 2026
CVE-2026-133120CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/express
NoYesNov 21, 2026
CVE-2026-133312MEDIUM5.3
  • JavaScript logoJavaScript
  • @fastify/rate-limit
NoYesNov 21, 2026
CVE-2026-133273LOW3.7
  • JavaScript logoJavaScript
  • @fastify/swagger-ui
NoYesNov 21, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management