CVE-2026-18427: @fastify/static vulnerable to route guard bypass via non-canonical path segments

Published Aug 6, 2026
·
Updated

@fastify/static before version 10.1.3 contains an incomplete fix for a previous route guard bypass. The static file handler rejected only parent directory segments, but it did not canonicalize dot segments, duplicate slashes, encoded dots, or backslashes before route matching and before delegating to the send layer. As a result, an unauthenticated attacker could request a file protected by a route based guard using a non canonical path form that misses the guarded route yet resolves back onto the protected file, disclosing its contents. Applications that protect a subtree of the static root with a route based guard are affected, while applications relying on the allowedPath option are not. This is fixed in @fastify/static 10.1.3, which canonicalizes the pathname, including rejecting backslashes, on the path used for routing and serving.

Affected Software

1 affected component
npm/@fastify/static<10.1.3

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.3

Event History

Aug 6, 2026
CVE Published
via MITRE·02:52 PM
Data Sourced
via MITRE·02:52 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-18427?

CVE-2026-18427 has a severity rating of high, with a score of 7.5.

2

What type of vulnerability is CVE-2026-18427?

CVE-2026-18427 is classified as a Path Traversal vulnerability.

3

How do I fix CVE-2026-18427?

To fix CVE-2026-18427, upgrade @fastify/static to version 10.1.3 or later.

4

What does CVE-2026-18427 affect?

CVE-2026-18427 affects the @fastify/static package prior to version 10.1.3.

5

What can happen if CVE-2026-18427 is exploited?

Exploitation of CVE-2026-18427 can lead to a route guard bypass, allowing unauthorized access to static files.

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