CVE-2026-67316

High

Description

axios is vulnerable to read-side prototype-pollution gadgets that can alter request construction when Object.prototype has already been polluted by a separate vulnerability or dependency. In the bodyless method aliases (axios.get(), axios.delete(), axios.head(), axios.options()), inherited data is read via (config || {}).data before config normalization, causing an attacker-controlled body to be sent on requests that did not set one. Additional low-level paths, only reachable when calling exported adapters/helpers (e.g. lib/adapters/http.js, unsafe/helpers/resolveConfig.js) directly with plain configs and no own proxy or paramsSerializer, can inherit polluted proxy values (routing requests through an attacker-controlled proxy) or paramsSerializer values (attacker-controlled URL serialization). These low-level gadgets do not reproduce through normal high-level axios calls on 1.15.2+. The issue is fixed in axios 1.18.0 and 0.33.0.

SeverityHigh
CVSS7.4
Exploit probability—
ProductAxios
PublishedAug 1, 2026
First seenAug 1, 2026

How to fix

Update
  • axios axios0.33.0, 1.18.0 or later
  • axios1.18.0, 0.33.0 or later

Affected products

ProductAffected versionsFixed in
axios axiosv < 0.33.0, 1.0.0 ≤ v < 1.18.00.33.0, 1.18.0
axiosnpm1.0.0 ≤ v < 1.18.0, v < 0.33.01.18.0, 0.33.0

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.