Quick answers
- Is CVE-2026-101898 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101898 being exploited in the wild.
- How severe is CVE-2026-101898?
- High severity, with a CVSS score of 4, published 28 September 2026.
- Which products and versions are affected?
- Axios 1.13.0 through 1.19.x; axios (npm) >= 1.13.0, < 1.20.0, SEMVER:introduced=1.13.0,fixed=1.20.0.
- Is there a fix for CVE-2026-101898?
- Yes. axios (npm): upgrade to 1.20.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-101898 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-101898?
- Check whether you run Axios or axios (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- axios (npm): upgrade to 1.20.0 or later
npm install axios@1.20.0
Technical details
The vulnerability exists in Axios's HTTP/2 request setup code, which does not consistently apply caller-supplied proxy configuration (config.proxy or environment variables) or custom DNS lookup policies (config.lookup) before invoking http2.connect(). An attacker with network-level access or control over application configuration could force HTTP/2 HTTPS requests to bypass proxy and DNS policy enforcement. The issue is patched in version 1.20.0.
Affected products
- axios Axios 1.13.0 through 1.19.x
Identifiers
- CVE-2026-101898
- GHSA-3pq3-5fj3-cg6v
Timeline
- 2026-08-12: patched: Fixed in version 1.20.0 via commit d19040b
- 2026-09-28: disclosed