Skip to content

chore(deps): update dependency fastify to v5.8.1 [security]#9574

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

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

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 3, 2026

This PR contains the following updates:

Package Change Age Confidence
fastify (source) 5.7.25.8.1 age confidence

GitHub Vulnerability Alerts

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

CVE-2026-3419

Description

Fastify incorrectly accepts malformed Content-Type headers containing trailing characters after the subtype token, in violation of RFC 9110 §8.3.1. For example, a request sent with Content-Type: application/json garbage passes validation and is processed normally, rather than being rejected with 415 Unsupported Media Type.

When regex-based content-type parsers are in use (a documented Fastify feature), the malformed value is matched against registered parsers using the full string including the trailing garbage. This means a request with an invalid content-type may be routed to and processed by a parser it should never have reached.

Impact

An attacker can send requests with RFC-invalid Content-Type headers that bypass validity checks, reach content-type parser matching, and be processed by the server. Requests that should be rejected at the validation stage are instead handled as if the content-type were valid.

Workarounds

Deploy a WAF rule to protect against this

Fix

The fix is available starting with v5.8.1.


Release Notes

fastify/fastify (fastify)

v5.8.1

Compare Source

⚠️ Security Release

Fixes "Missing End Anchor in "subtypeNameReg" Allows Malformed Content-Types to Pass Validation": GHSA-573f-x89g-hqp9.

CVE-2026-3419

Full Changelog: fastify/fastify@v5.8.0...v5.8.1

v5.8.0

Compare Source

What's Changed

New Contributors

Full Changelog: fastify/fastify@v5.7.4...v5.8.0

v5.7.4

Compare Source

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

v5.7.3

Compare Source

⚠️ Security Release
What's Changed

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


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 added the dependencies label Feb 3, 2026
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch 3 times, most recently from afaf200 to f6dae87 Compare February 10, 2026 15:08
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch 2 times, most recently from 58479cb to e92a1aa Compare February 17, 2026 21:09
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch 2 times, most recently from ea4894a to 2c5eaf1 Compare February 24, 2026 11:48
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch 4 times, most recently from 5f76311 to 43e7457 Compare March 6, 2026 01:26
@renovate renovate bot changed the title chore(deps): update dependency fastify to v5.7.3 [security] chore(deps): update dependency fastify to v5.8.1 [security] Mar 6, 2026
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch 4 times, most recently from 3b983d7 to 0b78715 Compare March 13, 2026 15:52
@renovate renovate bot force-pushed the renovate/npm-fastify-vulnerability branch from 0b78715 to 79db207 Compare March 17, 2026 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants