Incorrect Authorization Affecting wazuh-dashboard package, versions <4.14.10-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.35% (29th 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-22550187
  • published15 Nov 2026
  • disclosed13 Nov 2026

Introduced: 13 Nov 2026

NewCVE-2026-126358  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

Upgrade Chainguard wazuh-dashboard to version 4.14.10-r3 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 is a Web application framework that provides support for any JavaScript runtime. From 4.1.4 until 4.13.16, RegExpRouter can omit wildcard middleware in three version-specific cases: since 4.13.0, middleware using the explicit default parameter pattern in /api/:tenant{[^/]+}/admin/* is not applied to a route written as /api/:tenant/admin/:id; since 4.1.4, middleware on /admin/* is not applied to a route registered as /admin* for paths under /admin/; and since 4.4.0, a request path containing an encoded line terminator can reach the not-found handler without wildcard middleware. The default SmartRouter selects RegExpRouter for most applications, and the router's registration-time coverage calculation treated the first two matching pattern pairs as different while its compiled wildcard did not match line terminators in the third case. An unauthenticated client can reach a route handler or the not-found handler without authentication or authorization middleware registered on the wildcard path. TrieRouter, LinearRouter, and PatternRouter apply the middleware in the three described cases. This issue is fixed in version 4.13.16.