CVE-2026-3419: Fastify's Missing End Anchor in "subtypeNameReg" Allows Malformed Content-Types to Pass Validation
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.
Published Mar 5, 2026 · Updated Mar 6, 2026
Affected packages
fastify
- Ecosystem
- npm
- Affected
- >= 5.7.2, <= 5.8.0
- Fixed in
- 5.8.1
- Check
npm ls fastify
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to TarPeg007, jsumners, mcollina, UlisesGascon.
References
- https://github.com/fastify/fastify/security/advisories/GHSA-573f-x89g-hqp9
- https://github.com/fastify/fastify/commit/67f6c9b32cb3623d3c9470cc17ed830dd2f083d7
- https://httpwg.org/specs/rfc9110.html#field.content-type
- https://nvd.nist.gov/vuln/detail/CVE-2026-3419
- https://cna.openjsf.org/security-advisories.html
- https://github.com/advisories/GHSA-573f-x89g-hqp9
- https://www.cve.org/CVERecord?id=CVE-2026-3419
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-107832
fastify is vulnerable to header validation bypass via case-sensitive propertyNames
low3.7Oct 22, 2026CVE-2026-76169
fastify vulnerable to authentication bypass via malformed URLs reaching encapsulated not-found handlers
high7.5Sep 30, 2026CVE-2026-84428
fastify vulnerable to header validation bypass via incomplete schema case normalization
high7.5Sep 30, 2026CVE-2026-84469
fastify vulnerable to request validation bypass via skipped boolean false schemas
high7.5Sep 30, 2026CVE-2026-84504
fastify vulnerable to request body replacement via an async validation result collision
high8.1Sep 30, 2026CVE-2026-92081
fastify vulnerable to Denial of Service via unhandled exception on HTTP/2 trailer responses
medium5.9Sep 30, 2026
