CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCVE-2026-126358
Hono: RegExpRouter skips wildcard middleware for some route sets and for paths with an encoded line terminator
Medium (5.3) in honojs hono. Fixed in hono 4.13.16.
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.
Severity
- CWE
- CWE-863 Incorrect Authorization
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Not in the NVD yet
- Record from
- the CVE List, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126358 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126358?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126358?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126358 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-126358)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126358"><img src="https://cve.bz/cve/badge/CVE-2026-126358.svg" alt="CVE-2026-126358"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| honojs hono | >= 4.1.4, < 4.13.16 |
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-h7mg-cq63-vhpq | npm | hono | >=4.1.4 <4.13.16 | 4.13.16 |