fix(deps): update dependency fastify to v5.3.2 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
fastify (source)	5.3.0 -> 5.3.2

GitHub Vulnerability Alerts

CVE-2025-32442

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.

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

---

Release Notes

fastify/fastify (fastify)

v5.3.2

Compare Source

⚠️ Security Release ⚠️

Unfortunately, v5.3.1 did not include a complete fix for "Invalid content-type parsing could lead to validation bypass" and CVE-2025-32442. This is a follow-up patch to cover an edge case.

What's Changed

• docs: fix archived concurrently link to point to active repo by @​TimTeylor in https://github.com/fastify/fastify/pull/6063
• fix: treat space as a delimiter in content-type parsing by @​mcollina in https://github.com/fastify/fastify/pull/6064

New Contributors

• @​TimTeylor made their first contribution in https://github.com/fastify/fastify/pull/6063

Full Changelog: fastify/fastify@v5.3.1...v5.3.2

v5.3.1

Compare Source

⚠️ Security Release ⚠️

• Fix for "Invalid content-type parsing could lead to validation bypass" and CVE-2025-32442

What's Changed

• test: migrate logger options to node test runner by @​ilteoood in https://github.com/fastify/fastify/pull/6059
• test: migrate logger logging to node test runner by @​ilteoood in https://github.com/fastify/fastify/pull/6060
• test: convert custom parser 1 to node test runner by @​ilteoood in https://github.com/fastify/fastify/pull/6053
• test: custom querystring parser by @​ilteoood in https://github.com/fastify/fastify/pull/6054
• test: migrate stream 4 to node test runner by @​ilteoood in https://github.com/fastify/fastify/pull/6062
• test: migrate request logger to node test runner by @​ilteoood in https://github.com/fastify/fastify/pull/6058
• test: migrate custom parser 0 to node test runner by @​ilteoood in https://github.com/fastify/fastify/pull/6052
• test: migrate logger instantiation to node test runner by @​ilteoood in https://github.com/fastify/fastify/pull/6061

New Contributors

• @​ilteoood made their first contribution in https://github.com/fastify/fastify/pull/6059

Full Changelog: fastify/fastify@v5.3.0...v5.3.1

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2895d46

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR