@fastify/static versions 8.0.0 through 9.1.0 decode percent-encoded path separators (%2F) before filesystem resolution, while Fastify's router treats them as literal characters. This mismatch allows attackers to bypass route-based middleware or guards that protect files served by @fastify/static. For example, a route guard on a protected path can be circumvented by encoding the path separator in the URL. Upgrade to @fastify/static 9.1.1 to fix this issue. There are no workarounds.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NFastify Static
APPFastify8.0.0 – 9.1.1 (bez)
Related vulnerabilities
A redirect vulnerability in the `fastify-static` module version >= 4.2.4 and < 4.4.1 allows remote attackers t...
@fastify/static versions 8.0.0 through 9.1.0 allow path traversal when directory listing is enabled via the li...
A redirect vulnerability in the fastify-static module version < 4.2.4 allows remote attackers to redirect user...
@fastify/middie versions 9.1.0 through 9.3.2 decode the encoded slash %2F inside path parameter values before ...
@fastify/express versions 4.0.6 and earlier only rewrite the plugin prefix for middleware mount paths when the...