Update dependency @hono/node-server to v1.19.10 [SECURITY]#1636
Merged
renovate[bot] merged 1 commit intomainfrom Mar 5, 2026
Merged
Update dependency @hono/node-server to v1.19.10 [SECURITY]#1636renovate[bot] merged 1 commit intomainfrom
renovate[bot] merged 1 commit intomainfrom
Conversation
renovate
bot
force-pushed
the
renovate/npm-hono-node-server-vulnerability
branch
from
049be3c to
8d2286e
Compare
renovate
bot
force-pushed
the
renovate/npm-hono-node-server-vulnerability
branch
from
8d2286e to
39de4fa
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.19.9→1.19.10GitHub Vulnerability Alerts
CVE-2026-29087
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
%2Fas a literal string when matching routes, while the static handler decodes%2Finto/before resolving the filesystem path.Example request:
/admin%2Fsecret.htmlThis may:
/admin/*, but/admin/secret.htmlunder 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.
Release Notes
honojs/node-server (@hono/node-server)
v1.19.10Compare Source
Security Fix
Fixed an authorization bypass in Serve Static Middleware caused by inconsistent URL decoding (
%2Fhandling) between the router and static file resolution. Users of Serve Static Middleware are encouraged to upgrade to this version.See GHSA-wc8c-qw6v-h7f6 for details.
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - Between 07:00 AM and 04:59 PM, only on Monday, Tuesday, Wednesday, and Thursday ( * 7-16 * * 1,2,3,4 ) (UTC).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.