CVE-2026-90982: @fastify/static vulnerable to route guard bypass via path case-folding

Published Sep 17, 2026
·
Updated

@fastify/static is a Fastify plugin that serves static files from a configured root directory. In versions before 10.1.4, on a case-insensitive filesystem such as Windows or the default macOS volume, a route guard or allowedPath restriction can be bypassed by altering the letter case of a path segment. The route matcher is case-sensitive while the filesystem is not, so a request that changes the case of a protected segment does not match the guarded route and falls through to the static handler, yet the filesystem resolves it to the same protected file. As a result, an unauthenticated request can read a file that a route guard or allowedPath was configured to protect. The issue does not affect case-sensitive filesystems and is not a directory traversal, since nothing is served from outside the configured root. The issue is fixed in @fastify/static 10.1.4, which validates the requested path against its actual on-disk spelling and rejects case-aliased paths before authorization. As a workaround, serve static files from a case-sensitive filesystem, or ensure route guards and allowedPath rules account for every letter-case variant of the protected paths.

Affected Software

1 affected component
npm/@fastify/static<10.1.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade @fastify/static to a version that resolves this vulnerability.

    Fixed in 10.1.4
  2. Compensating control

    As a workaround on case-insensitive filesystems (e.g., Windows or default macOS volume), serve static files from a case-sensitive filesystem OR ensure route guards and allowedPath rules account for every letter-case variant of the protected paths to prevent route guard bypass via path case-folding.

Event History

Sep 17, 2026
CVE Published
via MITRE·06:55 AM
Data Sourced
via MITRE·06:55 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Deployments using @fastify/static before 10.1.4 on a case-insensitive filesystem are affected, including Windows and the default macOS volume. Case-sensitive filesystems are not affected.

2

What does an attacker need to exploit this issue?

An attacker can make an unauthenticated network request using altered letter case in a protected path segment. Exploitation relies on a route guard or allowedPath restriction protecting content served from the configured static root.

3

Can this expose files outside the configured static root?

No. This is not a directory traversal issue; it does not cause files outside the configured root directory to be served.

4

What can be done if upgrading is not immediately possible?

Serve static files from a case-sensitive filesystem, or make route guards and allowedPath rules cover every letter-case variation of protected paths. Upgrading to @fastify/static 10.1.4 applies validation against the actual on-disk path spelling before authorization.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203