CVE-2026-42037: axios · CRLF Injection
Affects axiosSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.15.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.3 |
|---|
- Patch
- Available – fixed in 1.15.1
CVSS:3.1/AV:N/AC:L/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.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| axios axios | Affected
| Fixed in
|
AI-suggested
Upgrade axios to version 1.15.1 or later, where this vulnerability is fixed. No other mitigations are indicated or required as the fix addresses the root cause by sanitizing CRLF sequences in the Content-Type header of multipart parts.
Description
Axios versions from 1.0.0 up to but not including 1.15.1 contain a CRLF injection vulnerability in the FormDataPart constructor. This occurs because the value.type property of a Blob/File-like object is directly interpolated into the Content-Type header of multipart form-data parts without sanitization of CRLF sequences. An attacker controlling this property can inject arbitrary MIME part headers, bypassing Node.js v18+ header protections. The issue is fixed in version 1.15.1.