CVE-2026-6410: @fastify/static vulnerable to path traversal in directory listing

Published Apr 16, 2026
·
Updated

@fastify/static versions 8.0.0 through 9.1.0 allow path traversal when directory listing is enabled via the list option. The dirList.path() function resolves directories outside the configured static root using path.join() without a containment check. A remote unauthenticated attacker can obtain directory listings for arbitrary directories accessible to the Node.js process, disclosing directory and file names. File contents are not disclosed. Upgrade to @fastify/static 9.1.1 to fix this issue. As a workaround, disable directory listing by removing the list option from the plugin configuration.

Other sources

Impact

@fastify/static v9.1.0 and earlier serves directory listings outside the configured static root when the list option is enabled. A request such as /public/../outside/ causes dirList.path() to resolve a directory outside the root via path.join() without a containment check.

A remote unauthenticated attacker can obtain directory listings for arbitrary directories accessible to the Node.js process, disclosing directory names and filenames that should not be exposed. File contents are not disclosed.

Patches

Upgrade to @fastify/static >= 9.1.1.

Workarounds

Disable directory listing by removing the list option from the plugin configuration.

GitHub

Affected Software

3 affected componentsFixes available
npm/@fastify/static>=8.0.0<=9.1.0
npm/@fastify/static>=8.0.0<=9.1.0
9.1.1
fastify fastify-static>=8.0.0<9.1.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 9.1.1
  2. Upgrade

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

    Fixed in 9.1.1
  3. Configuration

    Disable directory listing by removing the `list` option from the @fastify/static plugin configuration.

    @fastify/static list option = removed

Event History

Apr 16, 2026
CVE Published
via MITRE·01:29 PM
Data Sourced
via MITRE·01:29 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
Affected Software
Advisory Published
via GitHub·10:34 PM
Data Sourced
via GitHub·10:34 PM
DescriptionSeverityWeaknessAffected Software
Feb 13, 58282
Event
via FIRST·02:16 PM
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-6410?

The severity of CVE-2026-6410 is considered high due to its potential for directory traversal attacks.

2

How do I fix CVE-2026-6410?

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

3

What versions of @fastify/static are affected by CVE-2026-6410?

CVE-2026-6410 affects @fastify/static versions between 8.0.0 and 9.1.0 inclusive.

4

What type of vulnerability is CVE-2026-6410?

CVE-2026-6410 is a path traversal vulnerability that allows access to directories outside the configured static root.

5

How does CVE-2026-6410 impact my application?

CVE-2026-6410 can lead to unauthorized access to sensitive files within the server's file system.

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