Skip to content

chore(deps): update dependency @hono/node-server to v2.1.6 - #59

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/hono-node-server-2.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/hono-node-server-2.x

Conversation

@renovate

@renovate renovate Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@hono/node-server 2.1.4 → 2.1.6 age adoption passing confidence

Release Notes

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

v2.1.6

Compare Source

Security fixes

This release includes fixes for the following security issues:

Backslash in the request path is parsed as a path separator, bypassing path-based access control at a reverse proxy

Affects: all requests. The raw request-target was passed to the WHATWG URL parser, which treats a backslash in the path as / and resolves .. segments, so /admin\secret reached the application as /admin/secret. A reverse proxy that forwards the backslash unchanged applied its path-based rules to the original path. GHSA-jpvv-r467-5p4w

A request whose path contains a raw backslash is now rejected with 400 Bad Request, for HTTP/1.1, HTTP/2 and WebSocket upgrades. A percent-encoded backslash (%5C) and a backslash in the query string are still accepted.

WebSocket upgrade request-target starting with // replaces the host in c.req.url, bypassing Origin checks

Affects: upgradeWebSocket. The URL of an upgrade request was built by resolving the request-target against the Host header, so a request-target such as //attacker.example/ws set the host of c.req.url to a client-chosen value while routing still saw /ws. An application that compared Origin with the origin of c.req.url could be bypassed by a page on another site. GHSA-7v5p-43qr-wch5

The host of upgrade requests now comes from the Host header, as for ordinary requests.

Unhandled ECONNRESET on the socket during an asynchronous WebSocket upgrade crashes the process

Affects: upgradeWebSocket. While the application handled an upgrade request, the socket had no error listener. A client that reset the connection during asynchronous middleware caused an unhandled 'error' event and terminated the process. GHSA-qv5m-9pm6-hqp3

Error and close events on the socket are now handled while the application runs, and a pending upgrade is released when the socket closes.


The backslash fix also ships in @hono/node-server v1.19.18. Users of upgradeWebSocket are encouraged to upgrade to this version.

v2.1.5

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/node-server@v2.1.4...v2.1.5


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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.

@greptile-apps

greptile-apps Bot commented Oct 13, 2026

Copy link
Copy Markdown

PR author is not in the allowed authors list.

@renovate
renovate Bot force-pushed the renovate/hono-node-server-2.x branch 9 times, most recently from 364e7d8 to 1e814bf Compare October 24, 2026 22:13
@zen-agents zen-agents Bot added the tron:checked Tron's security check found no problem in this pull request's latest commit label Oct 26, 2026
@zen-agents

zen-agents Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Tron security check: passed for commit 8af8a7d.

@renovate renovate Bot changed the title chore(deps): update dependency @hono/node-server to v2.1.5 chore(deps): update dependency @hono/node-server to v2.1.6 Nov 2, 2026
@renovate
renovate Bot force-pushed the renovate/hono-node-server-2.x branch from 1e814bf to 8af8a7d Compare November 2, 2026 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tron:checked Tron's security check found no problem in this pull request's latest commit

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants