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: https://github.com/honojs/node-server/compare/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: https://github.com/honojs/node-server/compare/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)

• 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

Sourced from hono's releases.

v4.13.18

Security fixes

This release includes fixes for the following security issues:

validator() skips validation for requests whose Content-Type parameters are formatted differently

Affects: validator('json') and validator('form') in hono/validator. A Content-Type with whitespace before ;, a trailing ;, or an unusual parameter name was not recognized, so the validator saw an empty object while the handler could read all fields. This completes the fix for GHSA-4h7h-rv7c-7m2v. The validator now decides by the media type alone, as c.req.parseBody() does. GHSA-92p4-j3wq-jmqx

bodyLimit() keeps every transfer chunk of a request body in memory

Affects: bodyLimit() in hono/body-limit. A body sent in very small transfer chunks was retained as one object per chunk, so a request within the configured limit could exhaust memory. The body is now buffered in one array bounded by maxSize. GHSA-39q9-qp46-w8xg

mount() and app.mount() forward a wrong path when a custom getPath adds a prefix

Affects: mount() in hono/mount and app.mount() on 4.13.16 and 4.13.17. With a getPath that prepends a prefix such as the host name, one segment too many was removed from the forwarded path, so middleware scoped inside the mount prefix could be skipped. The prefix is removed from the routed path again. Paths that would change meaning when forwarded now get 400, and an optional regular expression parameter in a mount path throws. GHSA-h25j-2p75-qj33

serveStatic() serves a path that was decoded twice when allowPercentInPath is enabled

Affects: serveStatic() in hono/serve-static and the runtime adapters, only with allowPercentInPath: true. A malformed percent escape in the request path was decoded a second time, so a path that middleware registered on the encoded form did not see could still reach a static file. The file path must now be the same as the routed path, and otherwise the response is 404. GHSA-74fm-fwc7-3fwp

---

Users who rely on validator(), bodyLimit(), mount() with a custom getPath, or serveStatic() with allowPercentInPath are strongly encouraged to upgrade to this version.

Full Changelog: https://github.com/honojs/hono/compare/v4.13.17...v4.13.18

v4.13.17

What's Changed

• fix(cookie): match the __Secure- and __Host- prefixes case-insensitively in honojs/hono#5608
• fix(utils/url): do not match a query key across separators in honojs/hono#5607
• fix(etag,pretty-json): cancel the discarded response body in honojs/hono#5606
• fix(client): detect the JSON media type with whitespace before a parameter in honojs/hono#5609
• fix(timing): honor a precision of 0 in setMetric in honojs/hono#5363
• fix(utils/mime,ssg): match media types case-insensitively in honojs/hono#5449
• fix(timing): escape double quotes and backslashes in Server-Timing descriptions in honojs/hono#5478
• fix(etag): preserve commas within quoted entity tags in honojs/hono#5353
• fix(accepts): preserve exact media type quality over subtype wildcards in honojs/hono#5427
• fix(cookie): match the __Secure- and __Host- prefixes case-insensitively in CookieConstraint in honojs/hono#5611
• fix(jsx): add the CSP nonce to all scripts generated by ErrorBoundary in honojs/hono#5430
• fix(ssg): do not reuse created directories across toSSG runs in honojs/hono#5381
• fix(aws-lambda): sanitize non-ASCII header values in API Gateway v2 events in honojs/hono#5483
• fix(jsx): escape element and object attribute values in honojs/hono#5512
• fix(jsx): do not render ref objects as attributes in honojs/hono#5615
• fix(factory): keep independent return types for nine handlers in honojs/hono#5618

Full Changelog: https://github.com/honojs/hono/compare/v4.13.16...v4.13.17

v4.13.16

... (truncated)

• f6fbaf0 4.13.18
• 0809e48 test(serve-static) fix test (#5623)
• c7ff08f Merge commit from fork
• b982c02 Merge commit from fork
• 9aeb45b Merge commit from fork
• b0af6bb Merge commit from fork
• 61f7c59 4.13.17
• 1534ffa fix(factory): keep independent return types for nine handlers (#5618)
• eb754bd fix(jsx): do not render ref objects as attributes (#5615)
• 6cbe361 fix(jsx): escape element and object attribute values (#5512)
• Additional commits viewable in compare view

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.