Vulnerability in Fastify
CVE-2026-3419
Fastify incorrectly accepts malformed `Content-Type` headers containing trailing characters after the subtype token, in violation of RFC 9110 §8.3.1(https://httpwg.org/specs/rfc9110.html#field.content-type). 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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
EPSS exploit prediction
EPSS 0.004, 33.4th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Fastify — versions 5.7.2, 5.8.1
Weakness classification (CWE)
References
- github.com/fastify/fastify/security/advisories/GHSA-573f-x89g-hqp9 (Vendor Advisory)
- github.com/fastify/fastify/commit/67f6c9b32cb3623d3c9470cc17ed830dd2f083d7 (Patch)
- httpwg.org/specs/rfc9110.html (Technical Description)
- github.com/advisories/GHSA-573f-x89g-hqp9 (Patch, Vendor Advisory)
- cna.openjsf.org/security-advisories.html (Vendor Advisory)
- www.cve.org/CVERecord (VDB Entry)