@fastify/static information disclosure in dotfile directory listings
- Exploited
- No known exploitation
- Fix
- Fixed in 10.1.12
- Who is exposed
- Not reported
Summary
The @fastify/static plugin lets a remote attacker, without logging in, list the names of files and subdirectories, recursively, inside dot-directories that the operator denied, when directory listing is enabled. File contents stay protected, so only names such as version control, backup, and key file names are exposed.
Written by a model
Original 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.
What to do
Upgrade to a fixed version: 10.1.12.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130811 (@fastify/static vulnerable to information disclosure of denied dotfiles via directory listing), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130811 (entry last updated 2026-11-19):
Affected:
- npm package @fastify/static: fixed in 10.1.12
Fixed versions: 10.1.12.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130811 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130811 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fastify/fastify-static/security/advisories/GHSA-7533-p376-8gg5
- https://cna.openjsf.org/security-advisories.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130811
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130811"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach16/20@fastify/static: 8.8M downloads a week
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 86 if added to CISA KEV
- Would score about 81 if CISA's SSVC rates exploitation active
- Would score about 46 if advisories confirm default setups are exposed
Impact
- Widely used@fastify/static has 8.8m weekly downloads. npmjs.com
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · fastify/fastify-static · Advisory GHSA-7533-p376-8gg5 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130811 |
| Record | NVD · CVE-2026-130811 |
| Other links 1 | |
| Link | cna.openjsf.org · security-advisories.html |
Questions about CVE-2026-130811
Is CVE-2026-130811 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-130811?
@fastify/static (npm): before 10.1.12.
Source: cve.now feed data
How do I fix CVE-2026-130811?
Upgrade to a fixed version: 10.1.12.
Source: cve.now feed data
Related
- CVE-2026-18427@fastify/static vulnerable to route guard bypass via non-canonical path segments
- CVE-2026-15074@fastify/static vulnerable to route guard bypass via path traversal
- CVE-2026-6414@fastify/static vulnerable to route guard bypass via encoded path separators
- CVE-2026-115515@fastify/static vulnerable to route guard bypass via default index and extension resolution
- CVE-2026-90982@fastify/static vulnerable to route guard bypass via path case-folding
- CVE-2026-7120@fastify/static vulnerable to Authorization Bypass via Non-Canonical URL Paths
No corrections so far. Something wrong on this page? Report an error.