Skip to main content
VulnerabilityPublished

Trigger.dev: V1 coordinator default-secret unauth Socket.IO

Affects trigger.devSource GCVE Database

0

CVSS 9.2 Critical : upgrade to 4.5.4 as a priority.

Data as of 3 Oct 2026, 17:40 UTC

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

What to do

Upgrade trigger.dev to 4.5.4.

Affected software

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

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade all self-hosted Trigger.dev instances to version 4.5.4 or later, which removes the vulnerable V1 execution stack, eliminates the hardcoded default secrets, and disables the insecure coordinator namespaces and handlers. Managed cloud users do not need to take action as their deployments were not affected. Operators should verify that no deployments are running versions prior to 4.5.4 with default secrets.

Description

Trigger.dev versions prior to 4.5.4 contain multiple critical vulnerabilities in the self-hosted coordinator Socket.IO namespace. A hardcoded default secret allows unauthenticated access, enabling attackers to retrieve decrypted environment variables from any run if they know the run's internal ID. Additionally, unauthenticated write handlers allow attackers to send forged messages affecting arbitrary runs. These issues were fully resolved by removing the vulnerable V1 execution stack and default secrets in version 4.5.4. Managed cloud deployments were not affected due to non-default secrets.

References

Community reviews

Loading reviews…