Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 18, 2025

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 is behind base branch, 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 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 77060e3 to 4b95665 Compare April 24, 2025 09:49
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 4b95665 to ccf6f0b Compare May 19, 2025 21:29
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch 2 times, most recently from f677419 to a2a6ac1 Compare June 4, 2025 07:03
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from a2a6ac1 to 7de2a40 Compare July 2, 2025 15:00
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 7de2a40 to 758dfe5 Compare August 10, 2025 15:01
@socket-security
Copy link

socket-security bot commented Aug 10, 2025

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Critical
Critical CVE: npm form-data uses unsafe random function in form-data for choosing boundary

CVE: GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary (CRITICAL)

Affected versions: < 2.5.4; >= 3.0.0 < 3.0.4; >= 4.0.0 < 4.0.4

Patched version: 4.0.4

From: pnpm-lock.yamlnpm/form-data@4.0.1

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/form-data@4.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm buffer is 96.0% likely obfuscated

Confidence: 0.96

Location: Package overview

From: pnpm-lock.yamlnpm/aws-sdk@2.1692.0npm/buffer@4.9.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/buffer@4.9.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch 2 times, most recently from 2d1cfc3 to 626421a Compare August 19, 2025 16:32
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 626421a to 159faab Compare August 31, 2025 10:17
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 159faab to 4658eb2 Compare September 25, 2025 21:10
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 4658eb2 to 72d8521 Compare October 21, 2025 16:04
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 72d8521 to 2c1a9b2 Compare November 10, 2025 16:04
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 2c1a9b2 to 0978ea0 Compare December 3, 2025 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant