CVE-2026-3419
Fastify incorrectly accepts malformed `Content-Type` headers …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/fastify/fastify/security/advisories/GHSA-573f-x89g-hqp9
- github.com/fastify/fastify/commit/67f6c9b32cb3623d3c9470cc17ed830dd2f083d7
- httpwg.org/specs/rfc9110.html#field.content-type
- github.com/advisories/GHSA-573f-x89g-hqp9
- cna.openjsf.org/security-advisories.html
- www.cve.org/CVERecord?id=CVE-2026-3419
- nvd.nist.gov/vuln/detail/CVE-2026-3419
- nvd.nist.gov/vuln/detail/CVE-2026-3419
- cve.org/CVERecord?id=CVE-2026-3419
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.