Read the docs
TI-2026-57974 Aliases CVE-2026-84363GHSA-crvj-82cr-hjcx

Hono: Query parser reads parameters after the URL fragment, causing cache-key and proxy interpretation differentials

Priority LOW 27CWE-444Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub.

Summary

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.13.5, Hono's query helpers treat a question mark after a literal hash fragment as the start of a query string, so the application can read request parameters that browsers, new URL(), reverse proxies, filtering rules, parameter allow and deny lists, access logging, request validation, and other middleware do not observe. The Cache Middleware removes the fragment when building its cache key, allowing a response influenced by parameters inside the fragment to be stored under a key that omits those parameters and later served to other users. This can bypass filtering and auditing, poison cached responses, and enable stored cross-site scripting when an affected parameter is reflected into cached HTML without escaping. Exploitation requires a runtime and intermediary path that passes a literal hash character through to the request URL; Cloudflare Workers and intermediaries that strip fragments are not affected. This issue is fixed in version 4.13.5.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00448 39th percentileScored 2026-11-07
Fix Fixed hono (honojs): 4.13.5hono (npm): 4.13.5

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
honojshonobefore 4.13.54.13.5Patch availableCNA
—hono (npm)before 4.13.54.13.5Patch availableGHSA-crvj-82cr-hjcx
  • hono Vendorhonojs Affected before 4.13.5 Fixed in 4.13.5 Patch available CNA
  • hono (npm) Vendor— Affected before 4.13.5 Fixed in 4.13.5 Patch available GHSA-crvj-82cr-hjcx

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

  • Fix · CNA hono (honojs) Fixed in 4.13.5
  • Fix · GHSA-crvj-82cr-hjcx hono (npm) Fixed in 4.13.5 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-84363
  2. 2026-10-03 Alias added: GHSA-crvj-82cr-hjcx

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 59 →

Sources