[dependabot]

Bumps the npm-security group with 1 update in the / directory: @hono/node-server.

Updates @hono/node-server from 2.1.5 to 2.1.8

Release notes

Sourced from @​hono/node-server's releases.

v2.1.8

What's Changed

• fix(request): forward duplex to the native request in honojs/node-server#409
• fix(utils): do not chain a promise per chunk while streaming a response in honojs/node-server#417
• fix(listener): cancel the response body when the client has already disconnected in honojs/node-server#412
• fix(utils): cancel late HTTP/2 response bodies in honojs/node-server#419
• fix(listener): do not send a complete response when the body fails during the early read in honojs/node-server#420

Full Changelog: honojs/node-server@v2.1.7...v2.1.8

v2.1.7

Security fixes

This release includes a fix for the following security issue:

serveStatic with allowPercentInPath still allows the double-decode middleware bypass

Affects: serveStatic with allowPercentInPath: true. The fix for GHSA-rmxm-3fg6-px4f rejects a path containing %, but the allowPercentInPath option skipped that check entirely. A malformed percent sequence such as /static/%%36%31dmin/secret.txt was routed as /static/%61dmin/secret.txt, so middleware on /static/admin/* did not run, and serveStatic then decoded %61 to a and served static/admin/secret.txt. The default configuration was already fixed in 2.1.3. GHSA-fj57-4f93-cfw6

serveStatic now accepts the second decode only when its result equals the routed path with %25 replaced by %. File names containing a literal %, requested as %25, are served as before.

---

The same fix ships in hono v4.13.18 (GHSA-74fm-fwc7-3fwp).

Full Changelog: honojs/node-server@v2.1.6...v2.1.7

v2.1.6

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.

... (truncated)

Commits

• 1fc1dfc 2.1.8
• 3463817 fix(listener): do not send a complete response when the body fails during the...
• f22b99c fix(utils): cancel late HTTP/2 response bodies (#419)
• 4b885d3 fix(listener): cancel the response body when the client has already disconnec...
• 653ec79 fix(utils): do not chain a promise per chunk while streaming a response (#417)
• 7da431b fix(request): forward duplex to the native request (#409)
• abe63c8 2.1.7
• cc42986 Merge commit from fork
• 123f782 2.1.6
• cfaa79f Merge commit from fork
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[Copilot]

🟡 Changes recommended

The undocumented MSAL upgrade affects production authentication and falls outside the PR’s stated @hono/node-server-only scope, so it needs justification or separation into another PR.

1 open issue

• Document or separate the MSAL dependency upgrade · New

What changed in this PR

Updates dependencies for the Hono HTTP-adapter example and the SDK’s authentication stack, incorporating upstream Hono security and reliability fixes.

Changes:

• Bumps @hono/node-server from 2.1.5 to 2.1.8.
• Also bumps @azure/msal-node from 7.1.1 to 7.1.2 in the apps package and integration tests.
• Updates lockfile resolutions, including MSAL’s @azure/msal-common dependency to 16.15.0.

File	Description
test/​integration/​package.json	Updates the integration tests’ MSAL dependency.
packages/​apps/​package.json	Updates the apps package’s production MSAL dependency.
package-lock.json	Records updated Hono and MSAL dependency resolutions.
examples/​http-adapters/​package.json	Updates the Hono example’s Node server dependency.

_{Review effort: Balanced}