Vulnerability DatabaseCVE-2026-126358

CVE-2026-126358: 
JavaScript vulnerability analysis and mitigation

Overview

CVE-2026-126358 is an incorrect authorization vulnerability in the Hono web application framework's RegExpRouter component that allows unauthenticated attackers to bypass wildcard middleware (including authentication and authorization checks). It affects Hono versions >= 4.1.4 and <= 4.13.15 across all supported JavaScript runtimes. The vulnerability was published on November 1, 2026, and added to the GitHub Advisory Database on November 12, 2026. It carries a CVSS v3.1 base score of 5.3 (Medium) (Github Advisory, Feedly).

Technical details

The root cause is CWE-863 (Incorrect Authorization) in Hono's RegExpRouter, which is selected by default via SmartRouter for most applications. The vulnerability manifests in three distinct cases: (1) since v4.13.0, middleware using explicit default parameter patterns like /api/:tenant{[^/]+}/admin/* is not applied to routes written as /api/:tenant/admin/:id; (2) since v4.1.4, middleware on /admin/* is not applied to routes registered as /admin* for paths under /admin/; and (3) since v4.4.0, request paths containing encoded line terminators (%0A, %0D, %E2%80%A8, %E2%80%A9) bypass all wildcard middleware because the compiled wildcard regex did not match line terminator characters. The fix corrects coverage derivation from registered path structure and updates wildcard regex patterns from .* to [^]* to match line terminators, while also rejecting custom patterns that can match the empty string with UnsupportedPathError (Github Advisory, Patch Commit).

Impact

An unauthenticated remote client can reach route handlers or the not-found handler without passing through authentication or authorization middleware registered on wildcard paths. This primarily affects confidentiality, as unauthorized users may access restricted resources or API endpoints that should be protected. The vulnerability has no direct integrity or availability impact per the CVSS scoring, but the practical consequence depends on what the bypassed middleware was protecting — in the worst case, entire API surfaces (e.g., /api/:tenant/admin/*) could be exposed to unauthenticated access (Github Advisory, Hono Release).

Exploitability

No public proof-of-concept exploit code has been reported, and there is no evidence of in-the-wild exploitation at this time. The EPSS score is 0.0, indicating very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires no authentication, no user interaction, and low attack complexity — an attacker simply needs to craft HTTP requests matching the vulnerable route patterns or include encoded line terminators in the path (Github Advisory, Feedly).

Exploitation steps

  1. Reconnaissance: Identify Hono-based web applications running versions >= 4.1.4 and <= 4.13.15 using SmartRouter or RegExpRouter (the default). Look for API endpoints with wildcard-based middleware patterns such as /admin/* or /api/:tenant/admin/*.
  2. Identify vulnerable route patterns: Determine if the application registers middleware on wildcard paths (e.g., /admin/*) alongside routes like /admin* or /admin/:id, or uses explicit parameter patterns like /api/:tenant{[^/]+}/admin/*.
  3. Craft bypass request (Cases 1 & 2): Send an HTTP request directly to the route handler path (e.g., GET /api/acme/admin/42 or GET /admin/settings) that matches the handler route but not the middleware's coverage as computed by RegExpRouter, thereby skipping authentication middleware.
  4. Craft bypass request (Case 3): Send an HTTP request with an encoded line terminator in the path (e.g., GET /admin%0Asettings or GET /api/acme%0D/admin/42) to cause the RegExpRouter's compiled wildcard to fail to match, routing the request to the not-found handler or a route handler without invoking wildcard middleware.
  5. Access restricted resources: With middleware bypassed, interact with the protected route handler or API endpoint as an unauthenticated user, potentially reading sensitive data or performing restricted operations (Github Advisory, Patch Commit).

Indicators of compromise

  • Network: HTTP requests to protected API paths (e.g., /admin/, /api/*/admin/*) from unauthenticated clients that would normally be blocked by middleware; requests containing URL-encoded line terminators (%0A, %0D, %E2%80%A8, %E2%80%A9) in the path.
  • Logs: Access logs showing successful (2xx) responses to admin or restricted endpoints from unauthenticated sessions; requests to wildcard-protected paths that lack expected authentication headers (e.g., Authorization, session cookies).
  • Application Behavior: Absence of expected middleware log entries (e.g., auth checks, rate limiting) for requests that reached protected route handlers; 404 responses to paths containing encoded line terminators that should have been handled by wildcard middleware.

Mitigation and workarounds

Upgrade Hono to version 4.13.16, which corrects the RegExpRouter coverage logic and wildcard regex patterns for all three vulnerability cases (Hono Release). As an immediate workaround without upgrading, switch to TrieRouter by initializing the application with new Hono({ router: new TrieRouter() }), which correctly applies middleware in all three affected cases (Github Advisory). Note that if using PreparedRegExpRouter, its cached data must be regenerated after upgrading. Applications that do not rely on wildcard middleware for authentication or authorization are not affected.

Community reactions

The advisory was published by Hono maintainer yusukebe and credited to reporters quantumshiro, euriconicacio, and payku. The v4.13.16 release notes highlight this as one of five security fixes bundled in the release, indicating a coordinated security update effort by the Hono project (Hono Release). No significant broader media coverage or notable social media commentary has been identified beyond the GitHub advisory and release notes.

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

RHEL / CentOS

Affected

RHEL 10

Not Affected

Source: This report was generated using AI

Related JavaScript vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

GHSA-43rg-r2xr-q686MEDIUM5.9
  • JavaScript logoJavaScript
  • parse-server
NoYesNov 14, 2026
GHSA-pxwg-mv9c-h422LOWN/A
  • JavaScript logoJavaScript
  • @openeudi/openid4vp
NoYesNov 14, 2026
GHSA-qm7q-q8h9-jg8qMEDIUMN/A
  • JavaScript logoJavaScript
  • dompurify
NoYesNov 14, 2026
GHSA-662g-9vq2-39jxMEDIUMN/A
  • JavaScript logoJavaScript
  • qhhoj-backend
NoYesNov 14, 2026
GHSA-mh3m-3rhj-pqffLOWN/A
  • JavaScript logoJavaScript
  • qhhoj-backend
NoYesNov 14, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management