Skip to main content
VulnerabilityPublished

Trigger.dev Self-Hosted Deployment: Default Secrets allow Unauthenticated Infrastructure Compromise

Affects trigger.devSource GCVE Database

0

Public exploit available · CVSS 9.1 Critical : upgrade to 4.5.6 as a priority.

Data as of 3 Oct 2026, 17:40 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.5.6
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

What to do

Upgrade trigger.dev to 4.5.6.

Affected software

ProductAffectedFixed in
npmtrigger.devAffected
  • <4.5.6
Fixed in
  • 4.5.6

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 update trigger.dev to version 4.5.6 or later where this issue is fixed. Additionally, avoid deploying with default secrets from hosting/docker/.env.example. Replace all hardcoded secrets with unique, strong secrets and configure authentication for infrastructure services such as Redis and Postgres. Restrict network access to infrastructure containers and enable session validation features if applicable.

Description

Self-hosted trigger.dev version 4 instances deployed with the default Docker Compose configuration using hardcoded secrets in the provided .env.example file are vulnerable to unauthenticated attacks. The MAGIC_LINK_SECRET allows attackers to forge authentication tokens and gain access as any user without email verification. This leads to automatic user creation and full access to infrastructure services including the database, Redis, and ClickHouse, all of which use default or no authentication. The vulnerability enables complete infrastructure compromise, including tenant data, API keys, encrypted secrets, and job queue manipulation.

References

Community reviews

Loading reviews…