Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Primary rating from GitHub Advisory.
CVSS VectorGitHub Advisory
Lifecycle Timeline
6Blast Radius
ecosystem impact- 273 npm packages depend on axios (189 direct, 84 indirect)
Ecosystem-wide dependent count for version 1.0.0.
DescriptionGitHub Advisory
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 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.
AnalysisAI
Axios HTTP client versions prior to 1.15.1 and 0.31.1 use loose truthy/falsy comparison instead of strict boolean checks for the withXSRFToken config property, allowing XSRF tokens to be sent to cross-origin servers when the property is set to any truthy non-boolean value through prototype pollution or misconfiguration. This bypasses same-origin validation and enables attackers to exfiltrate XSRF tokens to attacker-controlled domains, compromising CSRF protection across applications using vulnerable versions.
Technical ContextAI
Axios implements XSRF (Cross-Site Request Forgery) token protection by validating that requests are same-origin before attaching XSRF tokens from cookies or custom headers. The vulnerability stems from CWE-183 (Permissive List of Allowed Inputs), where the withXSRFToken property evaluation uses JavaScript's truthy/falsy semantics (if (config.withXSRFToken)) instead of strict boolean comparison (if (config.withXSRFToken === true)). This allows any truthy value-including non-boolean values like strings, objects, or numbers-to pass the check. When withXSRFToken evaluates as truthy, the isURLSameOrigin check is bypassed entirely, causing tokens to be appended to all requests regardless of origin. The vulnerability affects both browser and Node.js environments where Axios is used (CPE: cpe:2.3:a:axios:axios:*:*:*:*:*:*:*:*). Prototype pollution attacks or direct misconfigurations can inject truthy values into this property.
RemediationAI
Upgrade Axios to version 1.15.1 or later for the 1.x branch, or 0.31.1 or later for the 0.x branch. These versions implement strict boolean comparison (if (config.withXSRFToken === true)) instead of truthy/falsy evaluation. Refer to the official GitHub Security Advisory at https://github.com/axios/axios/security/advisories/GHSA-xx6v-rp6x-q39c for detailed patching instructions. If immediate patching is not feasible, implement the following compensating controls: (1) Audit and lock your application's Axios configuration to ensure withXSRFToken is never set to non-boolean values-enforce this via configuration validation at application startup to catch misconfigurations early; (2) Disable or implement strict controls on prototype pollution attack surfaces by using Object.freeze() on configuration objects, Object.preventExtensions() on prototype chains, or adopting a library like deepfreeze for immutable config; (3) Implement Content Security Policy (CSP) headers with strict-dynamic and nonce-based script whitelisting to prevent unauthorized XSS-based prototype pollution attacks that could inject values into the Axios config; (4) Monitor HTTP request headers in your application logs for unexpected XSRF token presence in cross-origin requests and alert on anomalies. Note that workaround (2) introduces performance overhead and may conflict with legitimate dynamic configuration patterns, and workaround (3) requires browser support and careful rollout to avoid breaking legitimate functionality.
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Same weakness CWE-183 – Permissive List of Allowed Inputs
View allSame technique Information Disclosure
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-25607
GHSA-xx6v-rp6x-q39c