CVE-2026-18427Disclosure(fastify / fastify-static)

LOWCVSS 7.5 · HIGH

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Patch fastify fastify-static systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

@fastify/static before version 10.1.3 contains an incomplete fix for a previous route guard bypass. The static file handler rejected only parent directory segments, but it did not canonicalize dot segments, duplicate slashes, encoded dots, or backslashes before route matching and before delegating to the send layer. As a result, an unauthenticated attacker could request a file protected by a route based guard using a non canonical path form that misses the guarded route yet resolves back onto the protected file, disclosing its contents. Applications that protect a subtree of the static root with a route based guard are affected, while applications relying on the allowedPath option are not. This is fixed in @fastify/static 10.1.3, which canonicalizes the pathname, including rejecting backslashes, on the path used for routing and serving.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-22CWE-436

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • fastify-static

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 2 signals
  • Technical details provided in 2 signals
  • Disclosure: 1 classified signal
  • 2 total mentions across 1 day

Affected systems

Vendors
Products
fastify-static

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-08-06: 2Patch / Workaround · 2026-08-06: 2Technical Details · 2026-08-06: 208-06
Signal classification2 categories
Disclosure
150.0%
Patch
150.0%
Referenced assets1 URL
Full discourse2 posts
  • Ulises Gascón@kom_256
    Patch

    🚨 High-severity security fix in @fastify/static@10.1.3 just released! Patches CVE-2026-18427: route guard bypass via non-canonical path segments https://github.com/fastify/fastify-static/security/advisories/GHSA-423g-23ch-w7c6

    Post summary

    The advisory announces a high‑severity patch to fix CVE‑2026‑18427, a route guard bypass in fastify/static caused by non‑canonical path segments.

    01020297
    5.5K followersView on X
  • Upwind Security MDR@UpwindMDR
    Disclosure

    🚨HIGH - @fastify/static Route Guard Bypass via Non-Canonical Paths (CVE-2026-18427) @fastify/static <10.1.3 fails to fully canonicalize the request pathname before route matching/serving, allowing dot-segments, duplicate slashes, encoded dots, or backslashes to bypass route-based guards protecting a subtree of the static root and read restricted files. Apps not relying on route-level guards for static subpaths aren’t impacted. 👉Affected: @fastify/static < 10.1.3 | Upgrade to 10.1.3

    Post summary

    A high‑severity route guard bypass in @fastify/static <10.1.3 allows path traversal to read restricted files; upgrading to version 10.1.3 resolves the issue.

    0000099
    282 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appfastifyfastify-static---

Explore more