Inefficient Regular Expression Complexity Affecting wazuh-dashboard package, versions <4.14.10-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.41% (36th 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-22421731
  • published11 Nov 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

NewCVE-2026-119202  (opens in a new tab)
CWE-1333  (opens in a new tab)

How to fix?

Upgrade Chainguard wazuh-dashboard to version 4.14.10-r1 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.

@hapi/content provides HTTP Content-* header parsing. From 3.0.6 until 6.0.3, Content.disposition() uses an unanchored parameter-name expression in a global regular-expression scan, causing repeated failed matching over the remaining input when a Content-Disposition parameter contains a long token without an equals sign. The resulting quadratic processing can block the Node.js event loop before route handlers or validation when @hapi/pez parses multipart/form-data headers, including unauthenticated hapi routes with payload.multipart enabled, and also affects applications that pass untrusted headers directly to Content.disposition(). This issue is fixed in @hapi/content version 6.0.3.