@hono/node-server vulnerabilities

From 1.19.10 until 2.1.3, @hono/node-server's serveStatic decodes a request path a second time after Hono has already decoded it for routing, so a malformed percent-encoded sequence can make route middleware evaluate an encoded path while static file resolution uses a different directory. An unauthenticated attacker can bypass middleware mounted on a protected static prefix and read a file inside the configured static root.

@hono/node-server from version 2.0.0 to 2.0.10 has a vulnerability in WebSocket handling where an upgrade request with a missing or malformed Sec-WebSocket-Key header causes the request to remain in waiterMap with no cleanup path after the handshake is aborted. This allows an unauthenticated attacker to flood a public route, causing unbounded memory growth and service unavailability.

@hono/node-server before version 1.19.13 has a path handling inconsistency in serveStatic that allows protected static files to be accessed by using repeated slashes (//) in the request path. Route-based middleware may not match paths with repeated slashes, while serveStatic resolves them as normalized paths, leading to a middleware bypass.