Quick answers
- Is CVE-2026-101909 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101909 being exploited in the wild.
- How severe is CVE-2026-101909?
- High severity, with a CVSS score of 4, published 28 September 2026.
- Which products and versions are affected?
- Axios 0.28.0 to 0.34.0, 1.15.1 to 1.20.0; axios (npm) SEMVER:introduced=0.28.0,fixed=0.34.0.
- Is there a fix for CVE-2026-101909?
- Yes. axios (npm): upgrade to 0.34.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-101909 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-101909?
- 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 0.34.0 or later
npm install axios@0.34.0
Technical details
The ToFormData function in Axios 0.28.0–0.34.0 and 1.15.1–1.20.0 inherits serialization options (visitor, maxDepth, Blob handling) from the prototype chain, allowing an attacker with prototype-pollution capability to alter form data field naming, trigger request failures via maxDepth constraints, or corrupt value handling. The vulnerability requires a separate prototype-pollution entry point to set inherited properties; the attacker cannot directly inject functions but can modify inherited settings that affect serialization behavior. Fixed in versions 0.34.0 and 1.20.0.
Affected products
- Axios Axios 0.28.0 to 0.34.0, 1.15.1 to 1.20.0
Identifiers
- CVE-2026-101909
- GHSA-x97p-jq2g-jp4f
Timeline
- 2026-09-28: disclosed