CVE-2026-126210: @hono/node-server: Backslash in the request path is parsed as a path separator, bypassing path-based access control at a reverse proxy
Summary @hono/node-server passes the raw request-target to the WHATWG URL parser, which treats a backslash in the path as / and then resolves .. segments. A request for /admin\secret or /public\..\admin/secret reaches the application as /admin/secret.
Published Nov 12, 2026
Affected packages
@hono/node-server
- Ecosystem
- npm
- Affected
- >= 2.0.0, < 2.1.6
- Fixed in
- 2.1.6
- Check
npm ls @hono/node-server
@hono/node-server
- Ecosystem
- npm
- Affected
- < 1.19.18
- Fixed in
- 1.19.18
- Check
npm ls @hono/node-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
@hono/node-server passes the raw request-target to the WHATWG URL parser, which treats a backslash in the path as / and then resolves .. segments. A request for /admin\secret or /public\..\admin/secret reaches the application as /admin/secret. A reverse proxy that follows RFC 3986 forwards the backslash unchanged and applies its path-based rules to the original path, so the request reaches a route the proxy is meant to block.
Details
A raw backslash is not allowed in a request-target (RFC 3986, RFC 9112 Section 3.2.1), and RFC 9112 Section 3.2 says a recipient should reject such a request rather than correct it. Proxies such as nginx on Linux, HAProxy and Envoy keep the backslash as an ordinary character, so they and the application see different paths.
The fix responds with 400 Bad Request to a request whose path contains a raw backslash, for HTTP/1.1, HTTP/2, absolute-form request-targets and WebSocket upgrades. A percent-encoded backslash and a backslash in the query string are still accepted.
Impact
An unauthenticated client can reach a route that a reverse proxy, load balancer or WAF in front of the application blocks by path.
This affects applications served by @hono/node-server behind a front component that makes path-based decisions and forwards a backslash unchanged. Access control inside the Hono application, such as middleware on /admin/*, runs on the rewritten path and is not affected.
Credited to polamjag.
References
- https://github.com/honojs/node-server/security/advisories/GHSA-jpvv-r467-5p4w
- https://github.com/honojs/node-server/commit/3868998a805ae79216535ad3986c1e7228dee313
- https://github.com/honojs/node-server/commit/fb97395ec36af66567c76976e741110b02804d1c
- https://github.com/honojs/node-server/releases/tag/v1.19.18
- https://github.com/honojs/node-server/releases/tag/v2.1.6
- https://github.com/advisories/GHSA-jpvv-r467-5p4w
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-126343
@hono/node-server: Unhandled `ECONNRESET` on the socket during an asynchronous WebSocket upgrade crashes the process
medium5.3Nov 12, 2026CVE-2026-118663
@hono/node-server: `serveStatic` decodes the request path a second time, leading to bypass of middleware on static paths
medium5.3Oct 28, 2026CVE-2026-73565
Node.js Adapter for Hono: Unauthenticated memory-leak DoS via aborted WebSocket handshake
medium5.3Jul 21, 2026GHSA-frvp-7c67-39w9
Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`)
medium5.9Jul 21, 2026CVE-2026-39406
@hono/node-server: Middleware bypass via repeated slashes in serveStatic
medium5.3Apr 8, 2026CVE-2026-29087
@hono/node-server has authorization bypass for protected static paths via encoded slashes in Serve Static Middleware
high7.5Mar 4, 2026
