Uncaught Exception Affecting wazuh-dashboard package, versions <4.14.10-r5


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.45% (40th 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-22564792
  • published16 Nov 2026
  • disclosed12 Nov 2026

Introduced: 12 Nov 2026

NewCVE-2026-126343  (opens in a new tab)
CWE-248  (opens in a new tab)

How to fix?

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

@hono/node-server allows running the Hono application on Node.js. From 2.0.0 until 2.1.6, the WebSocket upgrade handler waits for the Hono application to finish asynchronous middleware or handler work without first attaching an error listener to the socket. If an unauthenticated client resets the TCP connection during that window, the socket emits an unhandled ECONNRESET error and terminates the Node.js process. If a global uncaughtException handler suppresses termination, the pending upgrade waiter is not released and repeated requests can grow the heap. This affects applications that enable WebSocket support and perform asynchronous work on the upgrade path. This issue is fixed in version 2.1.6.