Eomm

**Name of the Vulnerable Software and Affected Versions** fastify versions prior to 5.12.2 **Description** An issue exists where the object resolved by a successful Ajv async validator is treated as the value result protocol used by custom validator compilers. If a request that passes its route schema contains a property named `value` at the root, the software replaces the entire request body with the value of that property before the handler executes. This results in the handler receiving an object different from the one that satisfied the schema. An authenticated low-privilege caller can exploit this to replace the validated body with nested data, potentially triggering unauthorized operations, leading to unauthorized state changes and data disclosure. **Recommendations** Upgrade to fastify version 5.12.2 or later.

**Name of the Vulnerable Software and Affected Versions** Fastify versions 4.29.0 through 5.3.1 Fastify version 4.9.0 **Description** Fastify is a fast, low overhead web framework for Node.js. Applications specifying different validation strategies for different content types may bypass validation by providing a slightly altered content type, such as with different casing or altered whitespace before the semicolon (;). This issue affects applications using a specific schema pattern where individual content types are defined with their own schemas. The initial patch in version 5.3.1 did not fully address the problem, and a complete fix was released in version 5.3.2 and 4.29.1. **Recommendations** Fastify versions 4.29.0 through 5.3.1: Upgrade to version 5.3.2 or 4.29.1 to resolve the issue. Fastify version 4.9.0: Upgrade to version 4.9.1 to resolve the issue. As a workaround for all affected versions, avoid specifying individual content types in the schema.