Skip to main content
VulnerabilityPublished

CVE-2026-115515: @fastify/static · Incorrect Authorization

Affects @fastify/staticSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 10.1.8 when convenient.

Data as of 19 Nov 2026, 18:10 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (openjs)CVSS 3.15.3
Patch
Available – fixed in 10.1.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade @fastify/static to 10.1.8.

Affected software

ProductAffectedFixed in
@fastify/static@fastify/staticAffected
  • <10.1.8
Fixed in
  • 10.1.8
npm@fastify/staticpkg:npm/@fastify/staticOther threatsAffected
  • <10.1.8
Fixed in
  • 10.1.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade @fastify/static to version 10.1.8 or later, where the issue is fixed. As a workaround, deny access to the directory and extensionless forms in the allowedPath guard or disable the index and extensions options to prevent bypassing the guard.

Description

@fastify/static versions before 10.1.8 contain an incorrect authorization vulnerability where the allowedPath guard does not properly verify the final file served. This allows unauthenticated clients to access files intended to be private by requesting directory indexes or extensionless forms that bypass the guard. The issue is fixed in version 10.1.8.

References

Community reviews

Loading reviews…