@fastify/middie
@fastify/middie
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/middie, 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-85184 | 4 Sep 2026 | @fastify/middie: 9.1.0 < 9.3.4 | @fastify/middie: 9.3.4 | Update reference ↗ |
| CVE-2026-14181 | 1 Jul 2026 | 9.1.0 < 9.3.3 | 9.3.3 | Update reference ↗ |
| CVE-2026-14198 | 1 Jul 2026 | 9.1.0 < 9.3.3 | 9.3.3 | Update reference ↗ |
| CVE-2026-33804 | 16 Apr 2026 | < 9.3.2 | 9.3.2 | Update reference ↗ |
| CVE-2026-6270 | 16 Apr 2026 | < 9.3.2 | 9.3.2 | Update reference ↗ |
| CVE-2026-2880 | 27 Feb 2026 | 0.0.0 < 9.2.0 | No fixed version is explicitly recorded in the structured CVE data. | 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.