GHSA-m8m8-qj5v-23w3: axios (CVE-2026-101905)

Package	Ecosystem	Affected	Fixed in
axios	npm	>=1.15.2, <1.20.0	1.20.0

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The axios package on npm, versions from 1.15.2 before 1.20.0, has a flaw in its Node HTTP adapter: it does not set an own safe value for the createConnection option, so an inherited value from a polluted Object.prototype can be used by Node to open a socket. An attacker would first need a separate prototype-pollution flaw in the same Node.js process; with that, they could redirect later axios requests to their own server, receiving headers and bodies such as authorization tokens and returning responses to the application. Upgrade to axios 1.20.0, where the issue is fixed.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
7.6	High	4.0	CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N	CNA (GitHub_M)

CISA KEV Not listed.
EPSS 0.0042, the 36th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

31 Oct 2026, 13:34 UTC First seen by agentprime
31 Oct 2026, 13:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.