NPM · AUGUST 2026 · EARLY WARNING

Axios Prototype Pollution Vulnerability: Early Warning

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
GHSA-38GX-CFQF-F652GHSA-XJ6Q-8X83-JV6GSeverity: HIGH

Axios versions >=1.15.2 and <1.18.0 reportedly contain prototype-pollution read-side gadgets in Basic auth subfield handling, potentially allowing an attacker to inject Basic auth credentials.

What happened

Axios versions >=1.15.2 and <1.18.0 are under investigation for a potential vulnerability involving prototype pollution in the handling of Basic auth subfields. This issue appears to allow an attacker, who controls the polluted prototype values, to inject attacker-chosen Basic auth credentials or replace an existing Authorization header. To assess your exposure, check if your project dependencies include Axios within the affected version range. It is recommended to upgrade to axios@1.18.0 or later to mitigate this risk. For more details, consult the primary sources.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If axios is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats