Skip to content

chore(deps): update dependency fastify to v5.3.2 [security]#2659

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-fastify-vulnerability
Open

chore(deps): update dependency fastify to v5.3.2 [security]#2659
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-fastify-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 18, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
fastify (source) 5.2.1 → 5.3.2 age confidence

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

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
New Contributors

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

v5.3.1

Compare Source

⚠️ Security Release ⚠️
What's Changed
New Contributors

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

v5.3.0

Compare Source

What's Changed
New Contributors

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

v5.2.2

Compare Source

What's Changed
New Contributors

Full Changelog: fastify/fastify@v5.2.1...v5.2.2

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.

@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from de3f8ee to dcc77a2 Compare April 18, 2025 20:43
@renovate renovate bot changed the title chore(deps): update dependency fastify to v5.3.1 [security] chore(deps): update dependency fastify to v5.3.2 [security] Apr 18, 2025
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from dcc77a2 to e89eff9 Compare April 28, 2025 09:21
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from e89eff9 to 45a4722 Compare May 5, 2025 12:57
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 45a4722 to 7167571 Compare August 10, 2025 12:33
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 7167571 to 5283770 Compare September 15, 2025 08:18
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 5283770 to 9770c1e Compare October 21, 2025 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants