CVE-2026-84469: fastify vulnerable to request validation bypass via skipped boolean false schemas
Fastify decided whether to validate a request part by checking its schema for JavaScript truthiness. JSON Schema Draft 7 defines the boolean false as a valid schema that rejects every instance, but because false is falsy, a route that set body, querystring, params, or headers to false had that part left uncompiled: no validator was attached and the request reached the handler. An application that used false as a deny-all schema to make a route unreachable was therefore fully bypassed, and an unauthenticated remote client could reach the handler with any input. The same applied to the documented query alias for querystring. This is a complete bypass rather than a weak-schema issue, since false is the strongest JSON Schema assertion and must always fail.
References
- cna.openjsf.org/security-advisories.html
- github.com/advisories/GHSA-hwr6-493r-vm6h
- github.com/fastify/fastify/commit/7de6e81697778f9f41bd327a3b1c5c9a0d9637b4
- github.com/fastify/fastify/releases/tag/v5.12.2
- github.com/fastify/fastify/security/advisories/GHSA-hwr6-493r-vm6h
- nvd.nist.gov/vuln/detail/CVE-2026-84469
Code Behaviors & Features
Detect and mitigate CVE-2026-84469 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →