CVE-2026-84504: fastify vulnerable to request body replacement via an async validation result collision
Impact Fastify runs a route's validator and, for a result shaped like { value, error }, unwraps it: an error becomes a validation failure and value replaces the request part. This convention is intended for synchronous custom compilers (for example Joi). A JSON Schema $async validator, however, resolves with the validated data itself, so Fastify applied the same unwrapping to it.
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 runs a route's validator and, for a result shaped like { value, error }, unwraps it: an error becomes a validation failure and value replaces the request part. This convention is intended for synchronous custom compilers (for example Joi). A JSON Schema $async validator, however, resolves with the validated data itself, so Fastify applied the same unwrapping to it. If a request part validated by an $async schema contains a value property, Fastify replaced the whole request part with that nested value before the handler ran, so a value or error property in the payload was attacker-controlled. An application that dispatches operations from the validated request body could then act on data that never satisfied the route schema, leading to unauthorized state changes or disclosure. Reaching the vulnerable path requires the route to use an $async request schema.
Patches
Fastify no longer treats an asynchronous validation result as a { value, error } wrapper: an async validator's resolved value is used only to determine pass or fail, and it can no longer replace the request part or inject an error. The synchronous custom-compiler contract is unchanged. Patched in fastify 5.12.2 and 6.0.0.
Workarounds
If upgrading is not immediately possible, avoid $async request schemas, or perform the security-sensitive check in an onRequest or preHandler hook rather than relying on the schema-validated request part. Custom async validator compilers should signal failure by throwing (rejecting) rather than returning an { error } object.
Credited to velgusgus599, UlisesGascon, climba03003, mcollina.
References
- https://github.com/fastify/fastify/security/advisories/GHSA-667r-xxjv-c9mm
- https://nvd.nist.gov/vuln/detail/CVE-2026-84504
- https://github.com/fastify/fastify/commit/f02d8d4ab1ab208f10819c4dc213595b06497833
- https://cna.openjsf.org/security-advisories.html
- https://github.com/fastify/fastify/releases/tag/v5.12.2
- https://github.com/advisories/GHSA-667r-xxjv-c9mm
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-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-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
