Approved changes feed: RSS · Atom
cpe:2.3:a:fastify:fastify:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Fastify (51747187-798b-5030-972d-b19db43759b4) |
|---|---|
| Product | Fastify (e5289df8-251b-5a99-9d43-63d1c7962611) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/fastify/fastify-static |
purl2cpe | 2026-06-01 10:16:32.821574 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-107832 |
vulnerable | 2026-11-03 10:15:59.226379 |
fastify vulnerable to header validation bypass via case-sensitive propertyNames
LOW (3.7)
fastify is a fast and low overhead web framework for Node.js. In versions 5.12.2 through 5.12.5, the routine that lowercases header names declared in a route schema does not lowercase the enum or const header names nested inside a propertyNames subschema. As a result, a header allow-list or deny-list written with canonical (non-lowercase) casing never matches the incoming lowercased header, so a restricted header passes validation and reaches the route handler. An attacker can therefore bypass a case-sensitive header validation rule and smuggle a forbidden header past the schema, affecting the integrity of request handling. The issue is fixed in fastify 5.12.6, and users should upgrade to 5.12.6 or later. There is no workaround other than upgrading, though applications can declare header names in lowercase to avoid the mismatch.
Published: 2026-10-13T13:23:24.217Z
Updated: 2026-10-15T19:14:58.255Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-92081 |
vulnerable | 2026-10-13 12:28:53.817469 |
fastify vulnerable to Denial of Service via unhandled exception on HTTP/2 trailer responses
MEDIUM (5.9)
fastify is a fast and low-overhead web framework for Node.js. In versions before 5.12.5, when a route registers a response trailer via reply.trailer() and is served over HTTP/2, fastify unconditionally sets the Transfer-Encoding: chunked header, which is forbidden on HTTP/2, so Node.js throws while serializing the response headers. The exception is not caught and becomes an uncaughtException, so a single unauthenticated HTTP/2 request to any route that uses trailers crashes the server process and drops all in-flight requests, and it can be repeated on every restart. The issue is fixed in fastify 5.12.5, and users should upgrade to 5.12.5 or later. As a workaround, avoid registering response trailers with reply.trailer() on routes served over HTTP/2 until upgrading.
Published: 2026-09-16T08:52:49.757Z
Updated: 2026-09-16T14:00:59.305Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-3635 |
vulnerable | 2026-06-08 08:01:19.103677 |
Fastify request.protocol and request.host spoofable via X-Forwarded-Proto/Host from untrusted connections when trustProxy uses restrictive trust function
MEDIUM (6.1)
Summary
When trustProxy is configured with a restrictive trust function (e.g., a specific IP like trustProxy: '10.0.0.1', a subnet, a hop count, or a custom function), the request.protocol and request.host getters read X-Forwarded-Proto and X-Forwarded-Host headers from any connection — including connections from untrusted IPs. This allows an attacker connecting directly to Fastify (bypassing the proxy) to spoof both the protocol and host seen by the application.
Affected Versions
fastify <= 5.8.2
Impact
Applications using request.protocol or request.host for security decisions (HTTPS enforcement, secure cookie flags, CSRF origin checks, URL construction, host-based routing) are affected when trustProxy is configured with a restrictive trust function.
When trustProxy: true (trust everything), both host and protocol trust all forwarded headers — this is expected behavior. The vulnerability only manifests with restrictive trust configurations.
Published: 2026-03-23T13:53:00.386Z
Updated: 2026-03-23T15:30:10.526Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-3419 |
vulnerable | 2026-06-08 08:01:18.594329 |
Fastify's Missing End Anchor in "subtypeNameReg" Allows Malformed Content-Types to Pass Validation
MEDIUM (5.3)
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: 2026-03-06T17:50:58.714Z
Updated: 2026-03-09T14:55:21.011Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-33806 |
vulnerable | 2026-06-08 07:59:11.244984 |
fastify vulnerable to Body Schema Validation Bypass via Leading Space in Content-Type Header
HIGH (7.5)
Impact:
Fastify applications using schema.body.content for per-content-type body validation can have validation bypassed entirely by prepending a space to the Content-Type header. The body is still parsed correctly but schema validation is skipped.
This is a regression introduced in fastify >= 5.3.2 by the fix for CVE-2025-32442
Patches:
Upgrade to fastify v5.8.5 or later.
Workarounds:
None. Upgrade to the patched version.
Published: 2026-04-15T00:14:02.376Z
Updated: 2026-07-15T01:06:02.186Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25224 |
vulnerable | 2026-06-08 07:53:19.525107 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25223 |
vulnerable | 2026-06-08 07:53:19.523889 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-32442 |
vulnerable | 2026-06-08 07:18:59.798772 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41919 |
vulnerable | 2026-06-08 05:49:28.867466 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-39288 |
vulnerable | 2026-06-08 05:47:18.535836 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.