# hono/release
Hono v4.13.18
importance: criticalbreakingsecurity
This release fixes four security issues affecting request validation, body size limiting, mounted routing with custom path handling, and static file serving. The fixes prevent validation bypasses, memory exhaustion from chunked requests within the configured limit, incorrect forwarded paths, and access to static files through double-decoded paths.
affected
Users of `validator()`, `bodyLimit()`, `mount()` with a custom `getPath`, or `serveStatic()` with `allowPercentInPath` are affected.
action
Upgrade to v4.13.18, especially if you use any of the affected APIs or configurations.
release_signals
-For `mount()` and `app.mount()`, paths that would change meaning when forwarded now receive a 400 response, and an optional regular expression parameter in a mount path now throws.
!GHSA-92p4-j3wq-jmqx: `validator('json')` and `validator('form')` now determine content type by media type alone, preventing validation bypasses caused by unusual `Content-Type` parameter formatting. This completes the fix for GHSA-4h7h-rv7c-7m2v.
!GHSA-39q9-qp46-w8xg: `bodyLimit()` now buffers request data in one array bounded by `maxSize`, avoiding memory exhaustion from retaining one object per small transfer chunk.
!GHSA-h25j-2p75-qj33: `mount()` and `app.mount()` correct forwarded paths when a custom `getPath` adds a prefix, preventing middleware scoped inside the mount prefix from being skipped.
!GHSA-74fm-fwc7-3fwp: `serveStatic()` and runtime adapters now return 404 when the file path differs from the routed path, preventing access through double-decoded malformed percent escapes when `allowPercentInPath` is enabled.
# community_signal
How useful is this release to your stack?
—
net score
Sign in with GitHub to cast your vote.
Sign in with GitHub to vote
You’ll return to this release, then choose your vote.