Incorrect Authorization Affecting hono package, versions >=4.1.4 <4.13.16


Severity

Recommended
0.0
medium
0
10

CVSS assessment by Snyk's Security Team. Learn more

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 Learn

Learn about Incorrect Authorization vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-JS-HONO-22549651
  • published14 Nov 2026
  • disclosed12 Nov 2026
  • creditNakanishi Hiro, Eurico Nicacio, payku

Introduced: 12 Nov 2026

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

How to fix?

Upgrade hono to version 4.13.16 or higher.

Overview

hono is an Ultrafast web framework for the Edges

Affected versions of this package are vulnerable to Incorrect Authorization via RegExpRouter in three distinct cases where wildcard middleware is silently skipped, allowing a request to reach a route handler or the not-found handler without the authentication or authorization middleware registered on a wildcard path. In case 1, middleware whose parameter uses an explicit default pattern such as /api/:tenant{[^/]+}/admin/* is not applied to a route written as /api/:tenant/admin/:id. In case 2, middleware on /admin/* is not applied to a route registered on /admin* for paths under /admin/. In case 3, a path containing an encoded line terminator (%0A, %0D, %E2%80%A8, or %E2%80%A9) matches no wildcard pattern, so the request bypasses all wildcard middleware entirely.

Note: This is only exploitable when the application uses RegExpRouter directly or through the default SmartRouter, and relies on wildcard middleware for authentication or authorization.

Workaround

Instantiate Hono with TrieRouter explicitly: new Hono({ router: new TrieRouter() }).

CVSS Base Scores

version 4.0
version 3.1