Is CVE-2026-101907 exploited in the wild?

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

How severe is CVE-2026-101907?

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

Which products and versions are affected?

Axios 1.17.0 to 1.20.0; axios (npm) >= 1.17.0, < 1.20.0, SEMVER:introduced=1.17.0,fixed=1.20.0.

Is there a fix for CVE-2026-101907?

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

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

Am I affected by CVE-2026-101907?

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-101907: Axios fetch adapter maxRedirects bypass

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

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

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

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

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-101907 · Severity: high · CVSS 4 · Published 2026-09-28

Axios, a popular HTTP client library for JavaScript, contains a flaw in versions 1.17.0 through 1.20.0 where the fetch adapter ignores the maxRedirects: 0 setting and follows HTTP redirects anyway. An attacker could exploit this to access internal endpoints or retrieve sensitive responses that an application intended to block, potentially leading to unauthorized data access or unwanted state changes.

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

Quick answers

Is CVE-2026-101907 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-101907 being exploited in the wild.
How severe is CVE-2026-101907?: High severity, with a CVSS score of 4, published 28 September 2026.
Which products and versions are affected?: Axios 1.17.0 to 1.20.0; axios (npm) >= 1.17.0, < 1.20.0, SEMVER:introduced=1.17.0,fixed=1.20.0.
Is there a fix for CVE-2026-101907?: 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-101907 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-101907?: 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 the fetch adapter's handling of the maxRedirects configuration option. When maxRedirects is set to 0 (disabling redirects), the underlying fetch implementation continues to follow redirects, exposing internal responses or allowing access to internal state-changing endpoints. The issue is resolved in version 1.20.0 by properly honoring the maxRedirects: 0 setting and preventing automatic redirect following in the fetch adapter.

Affected products

Axios Axios 1.17.0 to 1.20.0

Identifiers

CVE-2026-101907
GHSA-r4gj-5m52-g5wh

Timeline

2026-09-28: disclosed
2026-08-12: patched: Fixed in version 1.20.0

References

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