Skip to main content
Menu
CVEs

@fastify/static remote code execution in static route guard

CVE-2026-115515Published November 19, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 10.1.8
Who is exposed
Not reported

Summary

The @fastify/static package, a Fastify plugin for serving static files, lets a request bypass its path guard by asking for a denied file's directory or extensionless form. An attacker can remotely, without logging in, read files inside the static root that the application meant to keep private.

Written by a model

Original description

@fastify/static is the Fastify plugin for serving static files. In versions before 10.1.8, the allowedPath guard receives only the requested pathname, but the underlying send step selects the file to serve afterwards, so a request for a directory resolves to its default index file and an extensionless request resolves through the configured extensions to a matching file. The selected file is streamed without being re-checked against allowedPath, so a guard that denies a specific file is bypassed by requesting its directory or extensionless form. An unauthenticated client can read files inside the static root that the application meant to keep private whenever the denied file is reachable as a directory index or an extension match. The issue is fixed in @fastify/static 10.1.8, and users should upgrade to 10.1.8 or later. As a workaround, also deny the directory and extensionless forms in allowedPath, or disable the index and extensions options.

What to do

Upgrade to a fixed version: 10.1.8.

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-115515 (@fastify/static vulnerable to route guard bypass via default index and extension resolution), 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-115515 (entry last updated 2026-11-19):
Affected:
- npm package @fastify/static: fixed in 10.1.8
Fixed versions: 10.1.8.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-115515 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115515 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-p497-qc9q-9hgx
- 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-115515
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-115515"}.

Affected versions

cve.now Index

41Pof 100 · provisional · methodology v3
  • 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

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · fastify/fastify-static · Advisory GHSA-p497-qc9q-9hgx
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-115515
RecordNVD · CVE-2026-115515
Other links 1
Linkcna.openjsf.org · security-advisories.html

Questions about CVE-2026-115515

Is CVE-2026-115515 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-115515?

@fastify/static (npm): before 10.1.8.

Source: cve.now feed data

How do I fix CVE-2026-115515?

Upgrade to a fixed version: 10.1.8.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.