Skip to main content
VulnerabilityPublished Updated

CVE-2026-42041: axios · Improper Authentication

Affects axiosSource GCVE Database

0
Compare

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

Data as of 12 Nov 2026, 00:35 UTC

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

Contested

Scorers differ by 2 or more points
CVSS scores by source
CNA (GitHub_M)CVSS 3.14.8
ADP (redhat-SADP)CVSS 3.18.2
Patch
Available – fixed in 1.15.1, 0.31.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

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

Description

Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, the Axios library is vulnerable to a Prototype Pollution "Gadget" attack that allows any Object.prototype pollution to silently suppress all HTTP error responses (401, 403, 500, etc.), causing them to be treated as successful responses. This completely bypasses application-level authentication and error handling. The root cause is that validateStatus is the only config property using the mergeDirectKeys merge strategy, which uses JavaScript's in operator — an operator that inherently traverses the prototype chain. When Object.prototype.validateStatus is polluted with () => true, all HTTP status codes are accepted as success. This vulnerability is fixed in 1.15.1 and 0.31.1.

References

Community reviews

Loading reviews…