cve.bz

CVE-2026-101899 axios axios: Protection Mechanism Failure

6.9 mediumEPSS 0.5%Fix available

Medium (6.9) in axios axios. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in axios 1.20.0.

On this page
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.

Severity

CVSS 4.0

6.9 medium
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
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-693 Protection Mechanism Failure
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-101899 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-101899?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-101899?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-101899 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
axios>= 1.15.0, < 1.20.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-44g4-m2mj-wpvxnpmaxios>=1.15.0 <1.20.01.20.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14node-axios1.20.0-1DEBIAN-CVE-2026-101899
Ubuntu26.10, Pro:20.04:LTS, Pro:22.04:LTS and 2 morenode-axiosno fix listedUBUNTU-CVE-2026-101899
Red Hathummingbird:1grafana12.40:12.4.12-0.4.hum1RHSA-2026:76677
Red Hathummingbird:1grafana13.10:13.1.7-0.1.hum1RHSA-2026:76448
Red Hathummingbird:1grafana13.20:13.2.3-0.1.hum1RHSA-2026:76430

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate information disclosure vulnerability was found in Axios, a promise-based HTTP client for Node.js that Red Hat Hardened Images (Hummingbird) ships as a dependency of its grafana12.4, grafana13.1, and grafana13.2 container images. Axios evaluates Classless Inter-Domain Routing (CIDR) notation entries in NO_PROXY proxy-bypass lists as textual hostname suffixes instead of IP address ranges. When a request targets an address covered by a CIDR entry in NO_PROXY while a proxy is configured, the CIDR bypass rule fails to match and the request is sent through the configured proxy. As a result, an adversary with access to the configured proxy server can observe and modify URLs, headers, and bodies of plaintext HTTP traffic intended for internal network services, and can observe connection metadata and CONNECT requests for HTTPS traffic. Red Hat rated this flaw as moderate severity (CVSS 6.5), consistent with the upstream assessment of moderate severity (CVSS 6.9). The resolution of this issue in the affected Hardened Images streams is delegated to the Hummingbird image maintainers, and a fix has been delivered through the affected image streams.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. The affected Red Hat Hardened Images releases containing the fix have been delivered; update to the latest grafana12.4, grafana13.1, and grafana13.2 image releases to resolve this issue.

ProductPackageStateAdvisory
Red Hat Hardened Imagesgrafana13-2-main-13.2.3-0.1.hum1Fixed 2026-10-05RHSA-2026:76430
Red Hat Hardened Imagesgrafana13-1-main-13.1.7-0.1.hum1Fixed 2026-10-05RHSA-2026:76448
Red Hat Hardened Imagesgrafana12-4-main-12.4.12-0.4.hum1Fixed 2026-10-06RHSA-2026:76677

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-101899.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-693 (17).

References

Check your stackJSON