Is CVE-2026-101901 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-101901 being exploited in the wild.

How severe is CVE-2026-101901?

High severity, with a CVSS score of 4, published 28 September 2026.

Which products and versions are affected?

Axios 1.13.0 to 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-101901?

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-101901 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-101901?

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.

CVE-2026-101901: Axios unhandled Http2Session error denial of service

Q: Is there a fix for CVE-2026-101901?

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.

Q: How is CVE-2026-101901 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-101901?

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.

CVE-2026-101901 · Severity: high · CVSS 4 · Published 2026-09-28

Axios, a widely-used HTTP client library for Node.js and browsers, fails to properly handle errors during HTTP/2 session initialization or reuse. An attacker or malicious service responding to HTTP/2 requests can trigger an unhandled error that crashes the Node.js process, causing a denial of service. Applications using Axios 1.13.0 through 1.19.x with HTTP/2 enabled are affected.

Technologies: Axios, axios (npm). Vendors: Axios, npm.

Quick answers

Is CVE-2026-101901 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-101901 being exploited in the wild.
How severe is CVE-2026-101901?: High severity, with a CVSS score of 4, published 28 September 2026.
Which products and versions are affected?: Axios 1.13.0 to 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-101901?: 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-101901 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-101901?: 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 Http2Session error handling during ClientHttp2Session initialization or reuse when httpVersion: 2 is used. Unhandled session errors escape Promise rejection handling and propagate as uncaught exceptions, terminating the Node.js process. The fix, delivered in version 1.20.0, adds proper error event handlers to the Http2Session to prevent unhandled errors from crashing the application.

Affected products

axios Axios 1.13.0 to 1.19.x

Identifiers

CVE-2026-101901
GHSA-542g-h47m-68v8

Timeline

2026-09-28: disclosed
2026-08-12: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.