Resource Exhaustion Affecting wazuh-dashboard-fips package, versions <4.14.7-r18
Threat Intelligence
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-19830197
- published16 Sept 2026
- disclosed1 Sept 2026
Introduced: 1 Sep 2026
NewCVE-2026-84364 (opens in a new tab)How to fix?
Upgrade Chainguard wazuh-dashboard-fips to version 4.14.7-r18 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.
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.13.5, when parseBody() expands dot-separated form field names into nested objects with dot-notation parsing enabled, it does not limit the nesting depth or the total number of intermediate objects created. Empty segments are preserved, so one deeply dotted field name can encode one nesting level per byte, while a large number of shallowly dotted fields can create the same amplification across a request. A request body within a normal size limit can therefore allocate an object graph far larger than the request after the body has already been accepted. An unauthenticated attacker who can reach an affected endpoint can send concurrent requests that exhaust the JavaScript heap, terminate the server process, and leave the service unavailable until restart. Dot-notation parsing is not enabled by default, and applications using the default behavior are not affected. This issue is fixed in version 4.13.5.