Axios is a ubiquitous HTTP library; flaw can enable same-process code execution and affects many apps and services across ecosystems.
CVE-2026-101909
Prototype-pollution in Axios toFormData can alter serialization and enable code execution.
Is CVE-2026-101909 being exploited?
Not confirmed. CVE-2026-101909 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-101909?
CVE-2026-101909 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-101909?
Yes. A fix has been recorded for CVE-2026-101909. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-101909 affect?
CVE-2026-101909 affects axios 0.28.0 - 0.33.x, axios 1.15.1 - 1.19.x, Node.js apps using affected axios, Browser apps bundling affected axios. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-101909?
Upgrade to axios >=0.34.0 or >=1.20.0; audit dependency trees.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Prototype pollution lets attackers change form-field naming/data, cause request failures, alter Blob handling, and—when combined with function-injection—execute code (potential RCE).
Patch when possible
- affected>= 1.15.1 and < 1.20.0
- affected>= 0.28.0 and < 0.34.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.