Update dependency @hono/node-server to v1.19.13 [SECURITY]#188
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Update dependency @hono/node-server to v1.19.13 [SECURITY]#188renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
994752d to
9bdb61e
Compare
9bdb61e to
38a6f5a
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.7→1.19.13@hono/node-server has authorization bypass for protected static paths via encoded slashes in Serve Static Middleware
CVE-2026-29087 / GHSA-wc8c-qw6v-h7f6
More information
Details
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.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
@hono/node-server: Middleware bypass via repeated slashes in serveStatic
CVE-2026-39406 / GHSA-92pp-h63x-v22m
More information
Details
Summary
A path handling inconsistency in
serveStaticallows protected static files to be accessed by using repeated slashes (//) in the request path.When route-based middleware (e.g.,
/admin/*) is used for authorization, the router may not match paths containing repeated slashes, whileserveStaticresolves them as normalized paths. This can lead to a middleware bypass.Details
The routing layer and
serveStatichandle repeated slashes differently.For example:
/admin/secret.txt=> matches/admin/*//admin/secret.txt=> may not match/admin/*This inconsistency allows a request such as:
to bypass middleware registered on
/admin/*and access protected files.Impact
An attacker can access static files that are intended to be protected by route-based middleware by using repeated slashes in the request path.
This can lead to unauthorized access to sensitive files under the static root.
This issue affects applications that rely on
serveStatictogether with route-based middleware for access control.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
honojs/node-server (@hono/node-server)
v1.19.13Compare Source
Security Fix
Fixed an issue in Serve Static Middleware where inconsistent handling of repeated slashes (
//) between the router and static file resolution could allow middleware to be bypassed. Users of Serve Static Middleware are encouraged to upgrade to this version.See GHSA-92pp-h63x-v22m for details.
v1.19.12Compare Source
What's Changed
Full Changelog: honojs/node-server@v1.19.11...v1.19.12
v1.19.11Compare Source
What's Changed
Full Changelog: honojs/node-server@v1.19.10...v1.19.11
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.
v1.19.9Compare Source
What's Changed
Full Changelog: honojs/node-server@v1.19.8...v1.19.9
v1.19.8Compare Source
What's Changed
New Contributors
Full Changelog: honojs/node-server@v1.19.7...v1.19.8
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.