CVE-2026-64145.9MediumCWE-177

CVE-2026-6414: @fastify/static vulnerable to route guard bypass via encoded path separators

@fastify/static

Vendor fix available · Affected: @fastify/static · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.4%probability of exploitation in the next 30 days

37th percentile

050100

Higher than 37% of scored CVEs

5.9MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

@fastify/static versions 8.0.0 through 9.1.0 decode percent-encoded path separators (%2F) before filesystem resolution, while Fastify's router treats them as literal characters. This mismatch allows attackers to bypass route-based middleware or guards that protect files served by @fastify/static. For example, a route guard on a protected path can be circumvented by encoding the path separator in the URL. Upgrade to @fastify/static 9.1.1 to fix this issue. There are no workarounds.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

@fastify/static · @fastify/staticfrom 8.0.0 before 9.1.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Handling of URL Encoding (Hex Encoding) · Injection and Smuggling
Vendor: @fastify/static
Published: April 2026
Band: Unlikely (under 1%), April 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-6414 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.