axios is vulnerable to Prototype Pollution
28
Low Risk
Request interceptors can replace the merged axios config with a plain object, including a spread clone such as {...config}. That drops the null-prototype container created at merge, so later reads of behavior options walk Object.prototype and treat inherited fields such as adapter, proxy, or transformResponse as trusted config. Class-based replacements and a foreign-realm Object.prototype whose constructor was mutated, deleted, or replaced by an accessor had the same gap. A polluted prototype can therefore hijack the transport or rewrite responses. Version 1.20.0 keeps a safe merged config by identity, snapshots interceptor replacements onto a null prototype, and ignores behavior inherited only from shared or foreign prototypes.
You are affected if you are using a version that falls within the vulnerable range.
axios is vulnerable to Prototype Pollution in versions 1.18.0 - 1.19.0.
Upgrade the axios library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.