Skip to main content
VulnerabilityPublished

CVE-2026-42036: axios · Unthrottled Resource Allocation

Affects axiosSource GCVE Database

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.15.1 or 0.31.1 when convenient.

Data as of 12 Nov 2026, 01:03 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.3
Patch
Available – fixed in 1.15.1, 0.31.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
axios axiosAffected
  • >=1.0.0 <1.15.1
  • <0.31.1
Fixed in
  • 1.15.1
  • 0.31.1

AI-suggested

Users should 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 enforces the maxContentLength limit correctly when using responseType: 'stream'.

Description

Axios versions prior to 1.15.1 and 0.31.1 have a vulnerability when using responseType: 'stream'. In these versions, Axios returns the response stream without enforcing the maxContentLength limit, allowing unbounded downstream consumption of response data. This issue is addressed in versions 1.15.1 and 0.31.1.

References

Community reviews

Loading reviews…