Intel

AIKIDO-2026-872099

axios is vulnerable to Prototype Pollution

Prototype Pollution Pre-CVE
Found by Aikido Intel before public disclosure or CVE publication.
Published 3 days ago

28

Low Risk

This Affects:

JSaxios
1.18.0 - 1.19.0
Fixed in 1.20.0
Are you affected? Scan for Free

TL;DR

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.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range.

Background info

axios is vulnerable to Prototype Pollution in versions 1.18.0 - 1.19.0.

How to fix this

Upgrade the axios library to the patch version.

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform