NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2025-32442: Fastify vulnerable to invalid content-type parsing, which could lead to validation bypass

highCVSS 3.1 7.5GHSA-mg2h-6x62-wpwc

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 ;.

Published Apr 18, 2025 · Updated May 29, 2025

Affected packages

fastify

Ecosystem
npm
Affected
>= 5.0.0, <= 5.3.1
Fixed in
5.3.2
Check
npm ls fastify

fastify

Ecosystem
npm
Affected
= 4.29.0
Fixed in
4.29.1
Check
npm ls fastify

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

Credited to Linkster78, climba03003, mcollina, Eomm, jsumners.

References

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 entries