CVE-2026-44490
MediumCVSS 4.8Exploitation Probability (EPSS)
Low risk20th percentile — higher than 20% of all known CVEs
Summary
Axios, a promise-based HTTP client, prior to versions 0.32.0 and 1.16.0, was vulnerable to prototype pollution attacks. As a result, polluted values could be silently captured and used in request headers.
Risk Assessment
Prototype pollution can lead to unpredictable application behavior and exposure of sensitive data. Organizations should be aware of the risks associated with using vulnerable versions of the library.
Recommendation
It is recommended to upgrade Axios to versions 0.32.0 or 1.16.0 to mitigate this vulnerability. Additionally, it is advisable to monitor project dependencies for similar issues.
Original NVD description (English source)
Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, axios exposes two read-side prototype-pollution gadgets. When Object.prototype is polluted by an upstream dependency in the same process (e.g. lodash _.merge / CVE-2018-16487), axios silently picks up the polluted values. (1) lib/utils.js line 406 builds merge()'s accumulator as result = {}, so result[targetKey] (line 414) walks Object.prototype and the polluted bucket's own keys are copied into the merged headers and ride out on the wire. (2) lib/core/mergeConfig.js line 26 builds the hasOwnProperty descriptor as a plain-object literal. Object.defineProperty reads descriptor.get/descriptor.set via the prototype chain, so a polluted Object.prototype.get or Object.prototype.set makes the call throw TypeError synchronously on every axios request. This vulnerability is fixed in 0.32.0 and 1.16.0.