CVE-2026-42042Public exploitNetwork attack vector

XSRF token disclosure via boolean coercion

Published Apr 24, 2026 · Updated Apr 24, 2026

Information disclosure in Axios before 0.31.1 and 1.0.0 through 1.15.0 allows remote attackers to steal XSRF tokens via cross-origin requests. The condition in lib/helpers/resolveConfig.js treats any truthy withXSRFToken value as explicit opt-in and skips isURLSameOrigin before adding the cookie value to request headers. Exploitation requires a browser application with an XSRF cookie and either prototype pollution or a truthy non-boolean configuration value; the leaked anti-CSRF token enables forged requests but not session hijacking.

CVSS severity5.4
Medium
EPSS probability0.23%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in Axios before 0.31.1 and 1.0.0 through 1.15.0 allows remote attackers to steal XSRF tokens via cross-origin requests. The condition in lib/helpers/resolveConfig.js treats any truthy withXSRFToken value as explicit opt-in and skips isURLSameOrigin before adding the cookie value to request headers. Exploitation requires a browser application with an XSRF cookie and either prototype pollution or a truthy non-boolean configuration value; the leaked anti-CSRF token enables forged requests but not session hijacking.

The record

CVE
CVE-2026-42042
Published
Apr 24, 2026
Updated
Apr 24, 2026
Vendor
Axios
Product
Axios
Classifications
CWE-201, CWE-183, T1185
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 24, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 0.31.1
  2. Affected versionversion=>= 1.0.0, < 1.15.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Axios · Axiosversion=< 0.31.1; version=>= 1.0.0, < 1.15.1

Published CVSS scores

5.4GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-201Insertion of Sensitive Information Into Sent Data
CWE-183Permissive List of Allowed Inputs
T1185Browser Session Hijacking

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo