Interpretation Conflict Affecting wazuh-dashboard-fips package, versions <4.14.5-r3
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-17268092
- published10 Jun 2026
- disclosed17 Jul 2026
Introduced: 10 Jun 2026
CVE-2026-44974 (opens in a new tab)How to fix?
Upgrade Chainguard wazuh-dashboard-fips to version 4.14.5-r3 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.
@hapi/content provided HTTP Content-* headers parsing. Prior to 6.0.2, Content.disposition() retained the last occurrence of each duplicate parameter while Content.type() retained the first occurrence of duplicate charset and boundary parameters, creating a parameter-smuggling primitive when another component in the request-processing chain resolves duplicates the opposite way. This can allow an upload filename allowlist bypass in headers such as Content-Disposition: form-data; name="file"; filename="safe.txt"; filename="shell.php". This issue is fixed in version 6.0.2.