@hono/node-server
Affected
- introduced
0, fixed1.19.10(semver)
Fixed versions
1.19.10
Fix
- Fixed version
1.19.10npm install @hono/[email protected]
Advisory
Also known as: CVE-2026-29087
@hono/node-server has authorization bypass for protected static paths via encoded slashes in Serve Static Middleware
Summary
When using @hono/node-server's static file serving together with route-based middleware protections (e.g. protecting /admin/*), inconsistent URL decoding can allow protected static resources to be accessed without authorization.
In particular, paths containing encoded slashes (%2F) may be evaluated differently by routing/middleware matching versus static file path resolution, enabling a bypass where middleware does not run but the static file is still served.
Details
The routing layer and the node-server static handler normalize request paths differently. The router preserves %2F as a literal string when matching routes, while the static handler decodes %2F into / before resolving the filesystem path.
Example request:
/admin%2Fsecret.htmlThis may:
/admin/*, but/admin/secret.html under the configured static root.This does not allow access outside the configured static root and is not a path traversal vulnerability.
Impact
An unauthenticated attacker could bypass route-based authorization protections for protected static resources by supplying paths containing encoded slashes.
Applications relying solely on route-based middleware to protect static subpaths under the same static root may have exposed those resources.
High Basis: The source's own band: HIGH
0, fixed 1.19.10 (semver)1.19.10
1.19.10npm install @hono/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0