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.
Affected products
axios: axios
References10
- github.com/axios/axios/security/advisories/GHSA-w9j2-pvgh-6h63 ExploitMitigationVendor Advisory
- github.com/axios/axios/security/advisories/GHSA-w9j2-pvgh-6h63 ExploitMitigationVendor Advisory
- access.redhat.com/errata/RHSA-2026:14937
- access.redhat.com/errata/RHSA-2026:16476
- access.redhat.com/errata/RHSA-2026:16532
- access.redhat.com/errata/RHSA-2026:16534
- access.redhat.com/errata/RHSA-2026:16535
- access.redhat.com/errata/RHSA-2026:16542
- access.redhat.com/errata/RHSA-2026:16874
- access.redhat.com/errata/RHSA-2026:17468
Metrics
- CVSS 3.1
-
6.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N - EPSS — exploit probability
- 1% percentile: 52 · as of 13 November 2026
- CWE
- CWE-287CWE-1321CWE-915
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.