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-18507890
  • published2 Aug 2026
  • disclosed1 Aug 2026

Introduced: 1 Aug 2026

NewCVE-2026-67319  (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 before 0.33.0 (and 1.x before 1.18.0) can consume inherited properties from nested request option objects when the JavaScript process's Object.prototype has already been polluted by another component. While the top-level merged config uses a null prototype, nested plain objects such as auth and paramsSerializer are cloned into ordinary objects and read without own-property checks. When an application passes placeholder nested objects such as auth: {} or paramsSerializer: {}, inherited username/password values can cause silent injection of an Authorization: Basic header, and inherited encode/serialize values can alter query-string serialization (full serializer replacement requires a function-valued pollution primitive). This is exploitable only in the presence of pre-existing prototype pollution.

CVSS Base Scores

version 3.1