CVE-2026-84428: fastify vulnerable to header validation bypass via incomplete schema case normalization
Impact Fastify lowercases header-schema property names before compiling the schema, because Node.js stores request header names in lowercase. That normalization was incomplete: it lowercased only top-level properties keys and the root required array, and did not lowercase the JSON Schema Draft 7 dependencies keyword (its trigger keys and dependent property names) or names in nested subschemas.
Published Sep 30, 2026
Affected packages
fastify
- Ecosystem
- npm
- Affected
- < 5.12.2
- Fixed in
- 5.12.2
- Check
npm ls fastify
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Fastify lowercases header-schema property names before compiling the schema, because Node.js stores request header names in lowercase. That normalization was incomplete: it lowercased only top-level properties keys and the root required array, and did not lowercase the JSON Schema Draft 7 dependencies keyword (its trigger keys and dependent property names) or names in nested subschemas. As a result, a header schema that uses dependencies to require one header when another is present (for example X-Admin requiring X-Admin-Token) never matches the lowercased request headers, so the dependency assertion is silently skipped. An unauthenticated remote client can send the header that activates a privileged path while omitting the header the dependency was meant to require, bypassing a schema-enforced security control. The header schema is idiomatic, valid JSON Schema Draft 7, and no custom validator, malformed request, or misconfiguration is required.
Patches
Header-schema names are now normalized across all schema positions (properties, required, dependencies, dependentRequired, dependentSchemas, and nested subschemas). Patched in fastify 5.12.2. The fix is also included in the 6.0.0 release. Header schemas referenced through an external shared $ref (registered with addSchema) are not reached by this normalization and now emit an FSTSEC002 startup warning; inline the header schema to keep case-insensitive assertions in effect.
Workarounds
If upgrading is not immediately possible, write header-schema names in lowercase so the dependencies and other case-sensitive assertions match Node's lowercased request headers, or enforce the cross-header requirement in an onRequest or preValidation hook instead of the schema.
Credited to schecthellraiser606, mcollina, UlisesGascon.
References
- https://github.com/fastify/fastify/security/advisories/GHSA-9q9j-q6p8-xq58
- https://nvd.nist.gov/vuln/detail/CVE-2026-84428
- https://github.com/fastify/fastify/commit/179619c8e99d54924309b9933402151ef9af37e0
- https://cna.openjsf.org/security-advisories.html
- https://github.com/fastify/fastify/releases/tag/v5.12.2
- https://github.com/advisories/GHSA-9q9j-q6p8-xq58
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-107832
fastify is vulnerable to header validation bypass via case-sensitive propertyNames
low3.7Oct 22, 2026CVE-2026-76169
fastify vulnerable to authentication bypass via malformed URLs reaching encapsulated not-found handlers
high7.5Sep 30, 2026CVE-2026-84469
fastify vulnerable to request validation bypass via skipped boolean false schemas
high7.5Sep 30, 2026CVE-2026-84504
fastify vulnerable to request body replacement via an async validation result collision
high8.1Sep 30, 2026CVE-2026-92081
fastify vulnerable to Denial of Service via unhandled exception on HTTP/2 trailer responses
medium5.9Sep 30, 2026CVE-2026-16732
fastify vulnerable to X-Forwarded-* spoofing under trustProxy hop-count
medium6.1Sep 2, 2026
