Skip to content

Linear-time path decoding, and fixes for trustProxy lists, the uuid matcher and route matching errors

Latest

Choose a tag to compare

@github-actions github-actions released this 19 Nov 06:39
Immutable release. Only release title and notes can be modified.

9.3.2 (2026-11-19)

Bug fixes

  • A request path with many encoded percent signs (%25) is now decoded in linear time. Before, a 16 KB path took about 6.5 ms of CPU, so unauthenticated clients could saturate a CPU core. (8ff0eb0)
  • trustProxy of defineConfig accepts a comma-separated list of ranges and an array of ranges. Before, both forms could fail when a request checked the trust policy. (#143)
  • router.matchers.uuid() rejects the letters after f. Before, /posts/gggggggg-gggg-gggg-gggg-gggggggggggg matched a route with a uuid matcher. (#144)
  • An error thrown while a route is matched, for example by the cast of a matcher, now reaches the error handler of the app also when the app has no global middleware. Before, the server logged it as fatal and sent a 500. (#146)

Performance

  • The server skips the tracing channels when nothing subscribes to them. A request through 10 global middleware is up to 18% faster on Node 26.10, and 2 to 4% faster on Node 26.12. (#147)

Full changelog: v9.3.1...v9.3.2