hono is vulnerable to HTTP Request Smuggling
59
Medium Risk
Hono's query string parser does not stop at the URL fragment, so a ? that appears after a # is treated as the start of the query string and fragment content is parsed as query parameters. This produces interpretation differences between Hono and upstream proxies, filters, or WAFs, and the cache middleware builds cache keys that drop the fragment. Requests carrying fragment-hidden parameters can bypass upstream controls or collide on cache keys so a cached response is served to unintended users. The fix stops query parsing at the fragment and preserves the fragment when constructing cache keys.
You are affected if you are using a version that falls within the vulnerable range and your runtime preserves a literal # in the incoming request URL so that fragment content reaches Hono's query parser.
hono is vulnerable to HTTP Request Smuggling in versions 0.0.1 - 4.13.4.
Upgrade the hono library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.