Cyber Resilience

CVE-2026-42042

Info Disclosure in Axios ≤ 0.31.1

Public PoCInfo Disclosure
Published
24 April 2026
Modified
27 April 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS Score 0.0023 14th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2026-42042 is a medium-severity Permissive List of Allowed Inputs (CWE-183) vulnerability in Axios Axios. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access ControlA06:2025 Insecure Design

EU & UK References

Vulnerability Data

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's XSRF token protection logic uses JavaScript truthy/falsy semantics instead of strict boolean comparison for the withXSRFToken config property. When this…

more

property is set to any truthy non-boolean value (via prototype pollution or misconfiguration), the same-origin check (isURLSameOrigin) is short-circuited, causing XSRF tokens to be sent to all request targets including cross-origin servers controlled by an attacker. This vulnerability is fixed in 1.15.1 and 0.31.1.

CWE(s)
CWE-183CWE-201

Related Threats

MITRE ATT&CK Enterprise Techniques

T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-44487Same product: Axios Axios
CVE-2026-42043Same product: Axios Axios
CVE-2026-44486Same product: Axios Axios
CVE-2024-39338Same product: Axios Axios
CVE-2025-27152Same product: Axios Axios
CVE-2023-45857Same product: Axios Axios
CVE-2026-44492Same product: Axios Axios
CVE-2026-42038Same product: Axios Axios
CVE-2026-42037Same product: Axios Axios
CVE-2024-57965Same product: Axios Axios

Affected Assets

axios
axios
≤ 0.31.1 · 1.0.0 — 1.15.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V4.4.2
  • V14.2.3

Mitigating Controls (NIST 800-53 r5) AI

AC-4 Information Flow Enforcement good match

Directly enforces policy-based information flow rules that block transmission of sensitive data to unauthorized actors.

AC-3 Access Enforcement good match

Enforces authorizations on logical access so that sensitive data is not released to unauthorized recipients.

SI-10 Information Input Validation good match

Strict validity checks on inputs directly stop overly permissive allow lists from being used as the protection mechanism.

SI-15 Information Output Filtering good match

Requires validation of outbound information to ensure sensitive content is not disclosed in responses or messages.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require rigorous allow-list design and testing that prevents permissive input validation.

DE.CM-09 partial match
prevents

Monitoring runtime data flows and outputs can detect sensitive data being transmitted.

PR.DS-02 partial match
prevents

Protecting data-in-transit can include filtering or encrypting to avoid exposing sensitive content.

PR.DS-10 partial match
prevents

Protecting data-in-use includes removing confidential values before they are processed or sent.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.11 Data masking mostly match
prevents

Data-masking techniques can prevent sensitive values from appearing in transmitted payloads.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect overly broad allow-lists, but does not inherently prevent their creation.

A.5.12 Classification of information partial match
mitigates

Classification identifies sensitive data so it is not inadvertently transmitted.

A.5.13 Labelling of information partial match
mitigates

Labelling makes sensitive data visible to developers and prevents accidental inclusion in outbound messages.

A.5.14 Information transfer partial match
mitigates

Information-transfer rules directly govern what data may be sent to external parties.

A.5.34 Privacy and protection of PII partial match
mitigates

PII-protection requirements reduce the chance of sending personal data to unauthorized recipients.

References