@fastify/static
@fastify/static
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at @fastify/static, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-90982 | 17 Sep 2026 | @fastify/static: < 10.1.4 | @fastify/static: 10.1.4 | Update reference ↗ |
| CVE-2026-18427 | 6 Aug 2026 | < 10.1.3 | 10.1.3 | Update reference ↗ |
| CVE-2026-15074 | 23 Jul 2026 | < 10.1.1 | 10.1.1 | Update reference ↗ |
| CVE-2026-7120 | 23 Jul 2026 | < 10.1.2 | 10.1.2 | Update reference ↗ |
| CVE-2026-6410 | 16 Apr 2026 | 8.0.0 < 9.1.1 | 9.1.1 | Update reference ↗ |
| CVE-2026-6414 | 16 Apr 2026 | 8.0.0 < 9.1.1 | 9.1.1 | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.