Trigger.dev: Unauthenticated Realtime Stream Data Injection via Run FriendlyId
Affects trigger.devSource GCVE Database
CVSS 5.3 Medium : upgrade to 4.5.5 when convenient.
Data as of 3 Oct 2026, 17:40 UTC
- Patch
- Available – fixed in 4.5.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NWhat to do
Upgrade trigger.dev to 4.5.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmtrigger.dev | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability. Users should upgrade to version 4.5.5 or later to ensure authentication is enforced and environment scoping is applied to the realtime stream POST handler. Until patched, restrict access to the endpoint and monitor for unauthorized data injection if possible.
Description
Trigger.dev versions prior to 4.5.5 have an unauthenticated POST endpoint allowing arbitrary data injection into realtime streams by anyone who knows or can guess a run friendlyId. The endpoint lacks authentication and environment scoping, enabling cross-environment access. This vulnerability has a medium severity with a CVSS score of 5.3.
References
- github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-59h8-w5q6-mfmp (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/pull/4250 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/commit/73d966ad226548b5f96fb5b4fc6fa607a3b7b8f8 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.5 (opens in a new tab)