CVE-2026-107832: fastify is vulnerable to header validation bypass via case-sensitive propertyNames
Impact Fastify lowercases header names in a headers schema before compilation, because Node.js stores request header names in lowercase. This normalization does not reach the header names held in a propertyNames subschema's enum and const.
Published Oct 22, 2026
Affected packages
fastify
- Ecosystem
- npm
- Affected
- >= 5.12.2, < 5.12.6
- Fixed in
- 5.12.6
- Check
npm ls fastify
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Fastify lowercases header names in a headers schema before compilation, because Node.js stores request header names in lowercase. This normalization does not reach the header names held in a propertyNames subschema's enum and const. A header-name deny-list written in the canonical header case, such as propertyNames: { not: { enum: ['X-Debug-Override'] } }, therefore never matches the lowercased request headers, and the forbidden header reaches the handler. Any application that uses a propertyNames deny-list or allow-list to constrain request header names does not get the constraint it expects. The same rule written in lowercase works, and the not: { required: [...] } form is unaffected, so this is a gap in the built-in normalization rather than a wrong schema. This is an incomplete fix of CVE-2026-84428 (GHSA-9q9j-q6p8-xq58), whose normalization covered header names used as property keys but not those used as values inside propertyNames.
Patches
Users should upgrade to fastify 5.12.6 or later, which lowercases header names held in enum and const inside a propertyNames subschema so they match the lowercased request headers. Header-name constraints that cannot be normalized automatically, regular expressions (propertyNames pattern and patternProperties keys) and a $ref used inside propertyNames, are documented and, for the $ref case, warned at startup (FSTSEC003). Author those to match the lowercased request headers.
Workarounds
Write the propertyNames header-name constraint in lowercase (for example enum: ['x-debug-override']), or enforce the header check in an onRequest or preValidation hook instead of the schema.
Credited to uttej-badwane, mcollina, UlisesGascon, kian0417.
References
- https://github.com/fastify/fastify/security/advisories/GHSA-389g-gv7q-r4x8
- https://nvd.nist.gov/vuln/detail/CVE-2026-107832
- https://github.com/fastify/fastify/pull/7104
- https://github.com/fastify/fastify/commit/3241fbd2f10a8ca1503533726836b53b6e8775a2
- https://github.com/fastify/fastify/commit/35c32375731c111439682b2f9e6e0baed2694269
- https://cna.openjsf.org/security-advisories.html
- https://github.com/fastify/fastify/releases/tag/v5.12.6
- https://github.com/advisories/GHSA-389g-gv7q-r4x8
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-76169
fastify vulnerable to authentication bypass via malformed URLs reaching encapsulated not-found handlers
high7.5Sep 30, 2026CVE-2026-84428
fastify vulnerable to header validation bypass via incomplete schema case normalization
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
