Protection Mechanism Failure Affecting wazuh-dashboard-fips package, versions <4.14.5-r7


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.22% (12th 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-18300831
  • published25 Jul 2026
  • disclosed23 Jul 2026

Introduced: 23 Jul 2026

NewCVE-2026-65899  (opens in a new tab)
CWE-693  (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.

DOMPurify 3.0.0 before 3.4.9 does not reset the retained Trusted Types policy when clearConfig() is called, so a DOMPurify instance reused across trust boundaries stays bound to a previously supplied TRUSTED_TYPES_POLICY. A later caller that requests RETURN_TRUSTED_TYPE output receives a TrustedHTML object created by the old (potentially unsafe) policy rather than a clean default, which can lead to script execution at a Trusted Types sink. Passing TRUSTED_TYPES_POLICY: null on the later call also does not clear the retained policy.

CVSS Base Scores

version 3.1