Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting wazuh-dashboard package, versions <4.14.6-r6


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.37% (30th 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-CHAINGUARDLATEST-WAZUHDASHBOARD-18598729
  • published9 Aug 2026
  • disclosed1 Aug 2026

Introduced: 1 Aug 2026

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

How to fix?

Upgrade Chainguard wazuh-dashboard to version 4.14.6-r6 or higher.

NVD Description

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

axios versions >=1.15.2 and <1.18.0 contain prototype-pollution read-side gadgets in Basic auth subfield handling (lib/adapters/http.js and lib/helpers/resolveConfig.js). When an application is already affected by a separate prototype-pollution primitive and makes an axios request with an own auth object that omits the username and/or password properties, axios reads the inherited Object.prototype.username and Object.prototype.password values and uses them to construct an outbound 'Authorization: Basic ...' header. axios itself does not pollute prototypes. The practical impact is outbound request tampering: an attacker who controls the polluted prototype values can inject attacker-chosen Basic auth credentials or replace an existing Authorization header. Credential disclosure is only possible under additional application-specific conditions.

CVSS Base Scores

version 3.1