Skip to content
Fencer Intel
medium 6.9

CVE-2026-101899 json

Axios: CIDR-form NO_PROXY entries are ignored, causing proxy exclusion bypass for internal IP ranges

published last mo. modified 24d ago also EUVD-2026-98835 , GHSA-44g4-m2mj-wpvx

cvss
6.9
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits
0
none known

Summary

Axios is a promise-based HTTP client for the browser and Node.js. From 1.15.0 until 1.20.0, Axios shouldBypassProxy treats the NO_PROXY CIDR form as a textual hostname suffix instead of evaluating the network range. A request targets an address covered by a CIDR entry in NO_PROXY while a proxy is configured. The CIDR bypass rule is not matched, so the request is sent through the configured proxy. For plaintext HTTP, the proxy can observe and modify URLs, headers, and bodies; for HTTPS, it can observe connection metadata and CONNECT requests. This issue is fixed in version 1.20.0.

Patch / fix

  • npm axios 1.20.0
  • axios axios 1.20.0
  • node-axios Debian 14 1.20.0-1

debian advisories DEBIAN-CVE-2026-101899

  • grafana12.4 hummingbird 1 12.4.12-0.4.hum1
  • grafana13.1 hummingbird 1 13.1.7-0.1.hum1
  • grafana13.2 hummingbird 1 13.2.3-0.1.hum1

red hat advisories RHSA-2026:76677RHSA-2026:76448RHSA-2026:76430

Is CVE-2026-101899 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-101899 updated cvss 6.5

axios: Axios: Information disclosure via improper CIDR proxy bypass handling

  • Red Hat Hardened Images grafana13.1 13.1.7-0.1.hum1, grafana13.2 13.2.3-0.1.hum1, grafana12.4 12.4.12-0.4.hum1
    fixed: vendor fix RHSA-2026:76677

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
26d ago

Exploit prediction

0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/axios/axios/security/advisories/GHSA-44g4-m2mj-wpvx referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 6.9 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N
CNA 4.0 6.9 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
npm axios
>=1.15.0, <1.20.0
1.20.0

Affected products

  • axios axios

Classification

Weakness
  • CWE-693 Protection Mechanism Failure

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.