[dependabot]

Bumps the npm_and_yarn group with 5 updates in the / directory:

Package	From	To
@hono/node-server	2.0.12	2.1.8
fast-uri	3.1.8	3.1.9
hono	4.13.8	4.13.18
ip-address	10.7.3	10.7.6
qs	6.16.0	6.16.2

Updates @hono/node-server from 2.0.12 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

Updates fast-uri from 3.1.8 to 3.1.9

Release notes

Sourced from fast-uri's releases.

v3.1.9

Security

This security release fixes four URI parsing and normalization vulnerabilities in fast-uri 3.x. Applications that process untrusted URI input should upgrade to v3.1.9.

• Medium — URI scheme spoofing through percent-encoded schemes (GHSA-w74x-v6f9-j3xg, CVE-2026-110306): percent-encoded scheme input is now rejected instead of being decoded into a live scheme.
• Medium — Host confusion during domain-host canonicalization (GHSA-wjr9-j795-jxcr, CVE-2026-110180): malformed domain hosts containing ambiguous delimiters or stripped control characters are now rejected instead of being silently rewritten.
• Low — Incorrect relative-reference normalization (GHSA-xhq7-xmqj-769h, CVE-2026-110095): dot-segment removal now preserves the resolution semantics of relative references.
• Low — Scheme injection in suffix references (GHSA-333x-w4r6-6crp, CVE-2026-110725): first-segment colons in path-only suffix references are now escaped so the output is not reparsed as a scheme.

Upgrade with:

npm install fast-uri@3.1.9

Thanks to @​zekth for reporting the scheme, host, and relative-reference issues, and to @​UlisesGascon for finding the suffix-reference issue and reviewing the remediations.

What's Changed

• ci: enable trusted publishing releases (v3.x) by @​mcollina in fastify/fast-uri#229

Full Changelog: fastify/fast-uri@v3.1.8...v3.1.9

Commits

• 0def703 Bumped v3.1.9
• a1d0da2 test: generate only relative path references
• 9eb8759 fix: preserve relative paths in suffix and relative resolution
• 54c30f7 docs: note suffix-reference authority ambiguity
• 39e6493 fix: escape a first-segment colon in suffix references
• 745183c test: cover first-segment colon in suffix references
• ddfc6a5 fix(SEC-03): reject non reg-name characters in domain hosts
• d86a8d2 fix: keep a colon-first segment behind "./" in relative normalization
• eb483b5 test: cover colon-first relative references in normalization
• b110a35 fix(SEC-02): preserve meaning of relative references during normalization
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for fast-uri since your current version.

Updates hono from 4.13.8 to 4.13.18

Release notes

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: honojs/hono@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: honojs/hono@v4.13.16...v4.13.17

v4.13.16

... (truncated)

Commits

• 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

Updates ip-address from 10.7.3 to 10.7.6

Release notes

Sourced from ip-address's releases.

v10.7.6

Full Changelog: beaugunderson/ip-address@v10.7.5...v10.7.6

v10.7.5

Full Changelog: beaugunderson/ip-address@v10.7.4...v10.7.5

v10.7.4

Full Changelog: beaugunderson/ip-address@v10.7.3...v10.7.4

Commits

• 3f12c6b 10.7.6
• 7b66931 Escape the characters the bad-character parse error highlights
• db0dbda 10.7.5
• 82a72d7 Read Teredo flags from the bits inspectTeredo names
• 172afdd Update mocha to 12 and patch vulnerable transitive dev dependencies
• 8c0ec94 Test that every parser rejects fullwidth and other non-ASCII digits
• 651c1dd 10.7.4
• ec80fcd Find an IPv6 zone by index so a rejected zone costs one pass
• e22eb4a Check generated docs without writing or hiding partial staging
• See full diff in compare view

Updates qs from 6.16.0 to 6.16.2

Changelog

Sourced from qs's changelog.

6.16.2

• [Fix] stringify: encode keys when allowEmptyArrays is set (#561)
• [meta] use double quotes for better OS support
• [Dev Deps] update evalmd, npmignore
• [Tests] stringify: pin allowEmptyArrays output for keys that need no encoding

6.16.1

• [Fix] parse: do not mutate an object input
• [Fix] stringify: stop re-encoding structural separator dots when encodeDotInKeys is set (#564)
• [Fix] stringify: arrayFormat: 'comma': pass the full encoder arguments with encodeValuesOnly
• [Fix] utils: encode + as %2B in iso-8859-1 mode so values round-trip (#565)
• [Fix] parse: only convert top-level dots to brackets when allowDots is on (#621)
• [Fix] stringify: ignore inherited array format names (#622)
• [Fix] stringify: arrayFormat: 'comma': do not throw on elements with no callable toString
• [Fix] utils: merge: seed an overflow container's index from its own keys, not just the source
• [Fix] utils: merge: keep a strictMerge conflict container's index and arrayLimit correct
• [Fix] parse: only treat [] as array syntax when it ends the key
• [Perf] decode: skip decoders when there is no percent sign (#583)
• [Robustness] utils: merge: apply arrayLimit to the two-element array built for colliding values
• [Robustness] parse: bound the nesting added by repeated strictMerge conflicts (credit @​Yeaseen)
• [Docs] document that qs and flat parsers disagree about parameter names
• [Docs] clarify that throwOnLimitExceeded limits each array, not the total number of values
• [Docs] clarify 6.14.1/6.15.2 parse bracket behavior change (#567, #568)
• [meta] fix changelog indents
• [actions] set least-privilege cache-mode
• [Tests] utils: decode: add missing cases
• [Tests] parse: characterize the ]= split when an = precedes any bracket group (#620)
• [Tests] parse: allowDots: cover stray close brackets before a dot
• [Dev Deps] update @ljharb/eslint-config, eslint, tape

Commits

• 136912a v6.16.2
• 6ed1c73 [Dev Deps] update evalmd, npmignore
• a09bc29 [meta] use double quotes for better OS support
• 5d3b1b9 [Fix] stringify: encode keys when allowEmptyArrays is set
• f13ec6c [Tests] stringify: pin allowEmptyArrays output for keys that need no enco...
• 2471b66 v6.16.1
• 51f736e [Docs] document that qs and flat parsers disagree about parameter names
• 40239f7 [Dev Deps] update tape
• d219359 [Fix] parse: do not mutate an object input
• 98157dc [Fix] stringify: stop re-encoding structural separator dots when `encodeDot...
• 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.