CVE-2026-42040: axios · Improper Encoding or Escaping of Output
Affects axiosSource GCVE Database
Not known to be exploited · CVSS 3.7 Low : 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 | 3.7 |
|---|
- Patch
- Available – fixed in 1.15.1, 0.31.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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 additional mitigation is required as the vulnerability is resolved in these versions.
Description
CVE-2026-42040 is a vulnerability in axios, a promise-based HTTP client for browsers and Node.js. The issue involves improper encoding in the encode() function, where a character mapping reverses safe percent-encoding of null bytes, converting %00 back to a raw null byte. This flaw exists in axios versions prior to 1.15.1 and 0.31.1. The vulnerability is fixed in versions 1.15.1 and 0.31.1. The impact is limited as the standard axios request flow is not affected.