Improper Input Validation Affecting wazuh-dashboard-fips package, versions <4.14.5-r7


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

Social Trends
EPSS
0.5% (39th 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-WAZUHDASHBOARDFIPS-17689967
  • published30 Jun 2026
  • disclosed11 Jun 2026

Introduced: 11 Jun 2026

CVE-2026-49982  (opens in a new tab)
CWE-20  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

Upgrade Chainguard wazuh-dashboard-fips to version 4.14.5-r7 or higher.

NVD Description

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

tmp is a temporary file and directory creator for node.js. In version 0.2.6, the _assertPath guard added to tmp rejects only string values that contain the substring ... It is bypassed when prefix, postfix, or template is supplied as a non-string value (Array, Buffer, or any object) whose includes('..') returns falsy but whose stringification still contains ../. The value flows through Array.prototype.join/String coercion inside _generateTmpName and path.join(tmpDir, opts.dir, name), producing a final path that escapes tmpdir and creates a file or directory at an attacker-controlled location with the host process's privileges. This affects any application that forwards untrusted request data (a common pattern is JSON body fields or qs-parsed bracket-array query strings such as ?prefix[]=...) into tmp.file, tmp.fileSync, tmp.dir, tmp.dirSync, tmp.tmpName, or tmp.tmpNameSync without explicit type coercion. This vulnerability is fixed in 0.2.7.