CVE-2026-42042: axios · Permissive List of Allowed Inputs
Affects axiosSource GCVE Database
Not known to be exploited · CVSS 5.4 Medium : upgrade to 1.15.1 or 0.31.1 when convenient.
Data as of 12 Nov 2026, 01:03 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.4 |
|---|
- Patch
- Available – fixed in 1.15.1, 0.31.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade axios to 1.15.1 or 0.31.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| axios axios | Affected
| Fixed in
|
AI-suggested
Upgrade Axios to version 1.15.1 or later, or 0.31.1 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause by enforcing strict boolean checks for the withXSRFToken property.
Description
Axios versions prior to 1.15.1 and 0.31.1 contain a vulnerability in their XSRF token protection logic. The issue arises because the withXSRFToken configuration property is evaluated using JavaScript truthy/falsy semantics rather than strict boolean comparison. This flaw can cause the same-origin check to be bypassed, resulting in XSRF tokens being sent to cross-origin servers, potentially controlled by attackers. The vulnerability is fixed in versions 1.15.1 and 0.31.1.