CVE-2026-130811 @fastify/static vulnerable to information disclosure of denied dotfiles via directory listing
Unauthenticated clients can list names of denied dot-directories in @fastify/static when directory listing is enabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Harmful if only installed
- No
- Needs a specific call
- Yes
- Fix
- None listed
What is CVE-2026-130811?
CVE-2026-130811 is a medium-severity information disclosure vulnerability in @fastify/static, published on 19 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
@fastify/static is the Fastify plugin for serving static files. In versions up to and including 10.1.11, when it is configured to deny or ignore dotfiles together with directory listing enabled, a request for a denied dot-directory returns its directory listing instead of being refused. The underlying send step answers with a forbidden response, but the listing fallback misreads that response on a path ending in a slash as a directory without an index file and serves the listing anyway. An unauthenticated client can enumerate the names of files and subdirectories, recursively, inside dot-directories the operator explicitly denied, such as version control, backup, and key file names. File contents remain protected and only names are disclosed. The issue is fixed in @fastify/static 10.1.12, and users should upgrade to 10.1.12 or later. As a workaround, disable directory listing or do not serve a root that contains dot-directories.
Weakness: CWE-548
Which versions are affected by CVE-2026-130811?
1 open source package ship an affected version, including %40fastify/static.
An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.
| Package | Affected | Fixed in |
|---|---|---|
%40fastify/static npmpkg:npm/%40fastify/static | All versions | 10.1.12 |
How do I fix CVE-2026-130811?
Upgrade each affected package to the fixed version listed for it above. Each package has its own fixed versions.
Upgrade, and rotate any secrets that may have been exposed. More about Information disclosure.
Is CVE-2026-130811 being exploited?
There is no known exploitation of CVE-2026-130811 in the wild and no public exploit code.
Sources
Also known as GHSA-7533-p376-8gg5.