CVE-2026-92081 Affecting trigger-dev package, versions <4.5.11-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.41% (33rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-TRIGGERDEV-20377430
  • published2 Oct 2026
  • disclosed16 Sept 2026

Introduced: 16 Sep 2026

CVE-2026-92081  (opens in a new tab)

How to fix?

Upgrade Minimos:latest trigger-dev to version 4.5.11-r1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream trigger-dev package and not the trigger-dev package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.