Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting node-axios package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.26% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-NODEAXIOS-18507888
  • published2 Aug 2026
  • disclosed1 Aug 2026

Introduced: 1 Aug 2026

NewCVE-2026-67316  (opens in a new tab)
CWE-1321  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest node-axios.

NVD Description

Note: Versions mentioned in the description apply only to the upstream node-axios package and not the node-axios package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1