Skip to content
Threat Brief

← All advisories

CVE-2026-126358

Medium 5.3No known exploitationFix available

Hono: RegExpRouter skips wildcard middleware for some route sets and for paths with an encoded line terminator

Vendor advisory: GHSA-h7mg-cq63-vhpq

Record last updated

CVSS score

5.3

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 29% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-863

Patching and mitigation

Patch status
Fix available (source: GitHub Advisory Database)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
honojshono>= 4.1.4, < 4.13.16Not documentedCVE Program
npmhonofrom 4.1.4 up to and including 4.13.154.13.16GitHub Advisory Database

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by GitHub Advisory Database

    Source: GitHub Advisory Database (opens in a new tab)

Vendor guidance and references