Skip to content

fix(deps): update dependency fastify to v5.7.3 [security] #737

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix(deps): update dependency fastify to v5.7.3 [security] #737

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

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

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
fastify (source) 5.2.1 → 5.7.3 age confidence
fastify (source) ^3.24.0 → ^5.7.3 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

CVE-2026-25223

Impact

A validation bypass vulnerability exists in Fastify where request body validation schemas specified by Content-Type can be completely circumvented. By appending a tab character (\t) followed by arbitrary content to the Content-Type header, attackers can bypass body validation while the server still processes the body as the original content type.

For example, a request with Content-Type: application/json\ta will bypass JSON schema validation but still be parsed as JSON.

This vulnerability affects all Fastify users who rely on Content-Type-based body validation schemas to enforce data integrity or security constraints. The concrete impact depends on the handler implementation and the level of trust placed in the validated request body, but at the library level, this allows complete bypass of body validation for any handler using Content-Type-discriminated schemas.

This issue is a regression or missed edge case from the fix for a previously reported vulnerability.

Patches

This vulnerability has been patched in Fastify v5.7.2. All users should upgrade to this version or later immediately.

Workarounds

If upgrading is not immediately possible, user can implement a custom onRequest hook to reject requests containing tab characters in the Content-Type header:

fastify.addHook('onRequest', async (request, reply) => {
  const contentType = request.headers['content-type']
  if (contentType && contentType.includes('\t')) {
    reply.code(400).send({ error: 'Invalid Content-Type header' })
  }
})

Resources

CVE-2026-25224

Impact

A Denial of Service vulnerability in Fastify’s Web Streams response handling can allow a remote client to exhaust server memory. Applications that return a ReadableStream (or Response with a Web Stream body) via reply.send() are impacted. A slow or non-reading client can trigger unbounded buffering when backpressure is ignored, leading to process crashes or severe degradation.

Patches

The issue is fixed in Fastify 5.7.3. Users should upgrade to 5.7.3 or later.

Workarounds

Avoid sending Web Streams from Fastify responses (e.g., ReadableStream or Response bodies). Use Node.js streams (stream.Readable) or buffered payloads instead until the project can upgrade.

References

Release Notes

fastify/fastify (fastify)

v5.7.3

Compare Source

⚠️ Security Release
What's Changed

Full Changelog: fastify/fastify@v5.7.2...v5.7.3

v5.7.2

Compare Source

⚠️ Notice ⚠️

Parsing of the content-type header has been improved to a strict parser in PR #​6414. This means only header values in the form described in RFC 9110 are accepted.

What's Changed

New Contributors

Full Changelog: fastify/fastify@v5.7.1...v5.7.2

v5.7.1

Compare Source

What's Changed

Full Changelog: fastify/fastify@v5.7.0...v5.7.1

v5.7.0

Compare Source

What's Changed

New Contributors

Full Changelog: fastify/fastify@v5.6.2...v5.7.0

v5.6.2

Compare Source

v5.6.1

Compare Source

What's Changed

New Contributors

Full Changelog: fastify/fastify@v5.6.0...v5.6.1

v5.6.0

Compare Source

What's Changed

New Contributors

Full Changelog: fastify/fastify@v5.5.0...v5.6.0

v5.5.0

Compare Source

What's Changed

New Contributors

Full Changelog: fastify/fastify@v5.4.0...v5.5.0

v5.4.0

Compare Source

What's Changed

Full Changelog: fastify/fastify@v5.3.3...v5.4.0

v5.3.3

Compare Source

What's Changed
New Contributors

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

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

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 these updates 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 •
edited
Loading

All alerts resolved. Learn more about Socket for GitHub.

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

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
@socket-security
Copy link

socket-security bot commented Dec 3, 2025 •
edited
Loading

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Addedfastify@​5.7.39810010097100

View full report

@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 0978ea0 to 541fa9b Compare December 31, 2025 14:56
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 541fa9b to 0f83609 Compare January 8, 2026 17:15
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 0f83609 to 658ed4d Compare January 19, 2026 17:50
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 658ed4d to 49ed3b6 Compare February 2, 2026 22:47
@renovate renovate bot changed the title chore(deps): update dependency fastify to v5.3.2 [security] fix(deps): update dependency fastify [security] Feb 2, 2026
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 49ed3b6 to e18349e Compare February 3, 2026 02:34
@renovate renovate bot changed the title fix(deps): update dependency fastify [security] fix(deps): update dependency fastify to v5.7.3 [security] Feb 3, 2026
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