Read the docs

Path handling in Hono mount() lets requests bypass scoped middleware

Priority LOW 24CWE-288Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-288.

Summary

Hono versions before 4.13.16 are affected, including the mount() and app.mount() functions. Their path rewriting can forward a crafted path to a mounted application that differs from the path the outer application routes, which is an authentication bypass using an alternate path (CWE-288). An unauthenticated remote client can use this to reach a mounted route without authentication or authorization middleware scoped to a subpath inside the mount prefix.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.13.16, mount() and app.mount() can remove a dynamic mount prefix using the route-pattern length rather than the matched-prefix length, allowing a crafted path to be forwarded as a protected inner route while the outer application routes the original path. Since 4.12.21, rebuilding the forwarded URL from the decoded pathname can also convert a decoded backslash to a slash and collapse parent-directory segments, again causing the mounted application to receive a protected path. An unauthenticated client can use either applicable path transformation to reach a mounted route without authentication or authorization middleware scoped to a subpath inside the mount prefix. This issue is fixed in version 4.13.16.

Why it matters now

EPSS 0.004 34th percentileScored 2026-11-16
Fix Fixed hono (honojs): 4.13.16hono (npm): 4.13.16

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
honojshonobefore 4.13.164.13.16Patch availableCNA
—hono (npm)before 4.13.164.13.16Patch availableGHSA-4m76-xfj5-7975
  • hono Vendorhonojs Affected before 4.13.16 Fixed in 4.13.16 Patch available CNA
  • hono (npm) Vendor— Affected before 4.13.16 Fixed in 4.13.16 Patch available GHSA-4m76-xfj5-7975

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:hono:hono:*:*:*:*:*:*:*:*——honojs
  • cpe:2.3:a:hono:hono:*:*:*:*:*:*:*:* Versions — — ·honojs

Remediation

Update the hono npm package to version 4.13.16, the fixed version listed for the affected ranges.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA hono (honojs) Fixed in 4.13.16
  • Fix · GHSA-4m76-xfj5-7975 hono (npm) Fixed in 4.13.16 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from CVE-2026-126357
  2. 2026-11-13 Alias added: GHSA-4m76-xfj5-7975
  3. 2026-11-13 Fix available: npm/[email protected] · GHSA-4m76-xfj5-7975
  4. 2026-11-13 CVSS score added · GHSA-4m76-xfj5-7975
  5. 2026-11-13 Weakness changed · GHSA-4m76-xfj5-7975
  6. 2026-11-13 4 new references · GHSA-4m76-xfj5-7975

References

  • TI-2024-21741 Hono vulnerable to Restricted Directory Traversal in serveStatic with deno CVSS 3.1MEDIUM 5.3
  • TI-2024-15441 @hono/node-server can't handle "double dots" in URL CVSS 3.1MEDIUM 5.3
  • TI-2024-32610 Hono vulnerable to bypass of CSRF Middleware by a request without Content-Type header. CVSS 3.1MEDIUM 5.9
  • TI-2024-29381 Hono CSRF middleware can be bypassed using crafted Content-Type header CVSS 3.1MEDIUM 5.0
  • TI-2026-39189 Hono: Lambda@Edge adapter keeps only the last value of a repeated request header, dropping the rest CVSS 3.1MEDIUM 4.8
  • TI-2026-23190 Hono: Arbitrary file access via serveStatic vulnerability CVSS 3.1CRITICAL 9.8
See all 67 →

Sources