Vulnerability record

CVE-2026-18427

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker snapshot: Aug 8, 2026.

What it is

Reported

@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.… Source description excerpt; complete tracked detail loads below.

NVD published: Aug 6, 2026 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

What is affected

Reported

@fastify/static — @fastify/static. Product-level identification only; no affected-version conclusion is available from this field.

NVD published: Aug 6, 2026 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Urgency and basis

Reported

Track · 119.0

Tracker decision tier from the evidence detailed below · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Exploitation evidence

Not reported

Not reported by tracked sources.

What to do

Not reported

Not reported by tracked sources.

Tracker guidance inferred from the decision tier: No action now. Remediate within standard update timelines. Monitor for change.

Evidence detail

Loading the full tracker evidence record…