Skip to content

chore(deps): update dependency @hono/node-server to v1.19.10 [security]#87

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-hono-node-server-vulnerability
Open

chore(deps): update dependency @hono/node-server to v1.19.10 [security]#87
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-hono-node-server-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 4, 2026

This PR contains the following updates:

Package Change Age Confidence
@hono/node-server 1.19.61.19.10 age confidence

GitHub 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 %2F as a literal string when matching routes, while the static handler decodes %2F into / before resolving the filesystem path.

Example request:

  • /admin%2Fsecret.html

This may:

  • fail to match middleware intended for /admin/*, but
  • still be resolved by the static handler as /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.


Release Notes

honojs/node-server (@​hono/node-server)

v1.19.10

Compare Source

Security Fix

Fixed an authorization bypass in Serve Static Middleware caused by inconsistent URL decoding (%2F handling) 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.9

Compare Source

What's Changed

Full Changelog: honojs/node-server@v1.19.8...v1.19.9

v1.19.8

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/node-server@v1.19.7...v1.19.8

v1.19.7

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/node-server@v1.19.6...v1.19.7


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Mar 4, 2026
@renovate renovate bot force-pushed the renovate/npm-hono-node-server-vulnerability branch from 99c52e6 to 1c6b0b7 Compare March 13, 2026 13:56
@renovate renovate bot changed the title chore(deps): update dependency @hono/node-server to v1.19.10 [security] chore(deps): update dependency @hono/node-server to v1.19.10 [security] - autoclosed Mar 27, 2026
@renovate renovate bot closed this Mar 27, 2026
@renovate renovate bot deleted the renovate/npm-hono-node-server-vulnerability branch March 27, 2026 01:30
@renovate renovate bot changed the title chore(deps): update dependency @hono/node-server to v1.19.10 [security] - autoclosed chore(deps): update dependency @hono/node-server to v1.19.10 [security] Mar 30, 2026
@renovate renovate bot reopened this Mar 30, 2026
@renovate renovate bot force-pushed the renovate/npm-hono-node-server-vulnerability branch 2 times, most recently from 1c6b0b7 to c98d288 Compare March 30, 2026 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants