fastify
Affected
- introduced
5.0.0, fixed5.3.2(semver)
Fixed versions
5.3.2
Fix
- Fixed version
5.3.2npm install [email protected]
Advisory
Also known as: CVE-2025-32442, CVE-2026-33806, GHSA-247c-9743-5963
Fastify vulnerable to invalid content-type parsing, which could lead to validation bypass
Impact
In applications that specify different validation strategies for different content types, it's possible to bypass the validation by providing a _slightly altered_ content type such as with different casing or altered whitespacing before ;.
Users using the the following pattern are affected:
fastify.post('/', {
handler(request, reply) {
reply.code(200).send(request.body)
},
schema: {
body: {
content: {
'application/json': {
schema: {
type: 'object',
properties: {
'foo': {
type: 'string',
}
},
required: ['foo']
}
},
}
}
}
})
User using the following pattern are not affected:
fastify.post('/', {
handler(request, reply) {
reply.code(200).send(request.body)
},
schema: {
body: {
type: 'object',
properties: {
'foo': {
type: 'string',
}
},
required: ['foo']
}
}
})
Patches
This was patched in v5.3.1, but unfortunately it did not cover all problems. This has been fully patched in v5.3.2.
Version v4.9.0 was also affected by this issue. This has been fully patched in v4.9.1.
Workarounds
Do not specify multiple content types in the schema.
References
_Are there any links users can visit to find out more?_
https://hackerone.com/reports/3087928
High Basis: The source's own band: HIGH
5.0.0, fixed 5.3.2 (semver)5.3.2
5.3.2npm install [email protected]4.29.0, fixed 4.29.1 (semver)4.29.1
4.29.1npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0