CVE Tools

CVE-2026-42037

Axios: CRLF Injection in multipart/form-data body via unsanitized blob.type in formDataToStream

No known exploitation. EPSS puts it in the 26th percentile. Fixed in 1.15.1.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • AxiosAffected: ≥ 1.0.0, < 1.15.1Upgrade to: 1.15.1Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether your applications use axios 1.0.0 through before 1.15.1 and forward files or form submissions from users.
  2. Upgrade axios to version 1.15.1.
  3. If upgrading is delayed, reject file type values containing line breaks before sending multipart uploads.
  4. Test upload and proxy workflows after the update.
npm install axios@1.15.1

What it is

From the CVE record

Axios is a promise based HTTP client for the browser and Node.js. From 1.0.0 to before 1.15.1, the FormDataPart constructor in lib/helpers/formDataToStream.js interpolates value.type directly into the Content-Type header of each multipart part without sanitizing CRLF (\r\n) sequences. An attacker who controls the .type property of a Blob/File-like object (e.g., via a user-uploaded file in a Node.js proxy service) can inject arbitrary MIME part headers into the multipart form-data body. This bypasses Node.js v18+ built-in header protections because the injection targets the multipart body structure, not HTTP request headers. This vulnerability is fixed in 1.15.1.

In plain language

Written by AI from the record

axios versions 1.0.0 through before 1.15.1 can let a malicious upload alter parts of an outgoing file submission; small businesses should update if they relay user uploads.

CWE-93 CRLF injection in axios multipart serialization allows an attacker-controlled Blob/File-like `type` value to inject arbitrary MIME-part headers in `formDataToStream`.

If you're affected

  • Altered upload metadata
  • Manipulated multipart requests
  • Downstream processing errors

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS26th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.3% chance of exploitation activity in the next 30 days, which ranks it in the 26th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 146 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Workaround availablerecord updated
  3. Publishedweakness classified

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Scored 5.3 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Axios, not every advisory.