Critical Vulnerability in Trigger.dev: Default Secret Authentication Flaw Exposes Sensitive Data
Summary
GHSA-gg6r-gp4c-89hp: Trigger.dev: V1 coordinator default-secret unauth Socket.IO. Affects trigger.dev versions < 4.5.4. Fixed in 4.5.4. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Trigger.dev is an open-source platform designed for building and managing workflows in web applications. It allows developers to automate tasks and integrate various services seamlessly. However, a significant vulnerability has been identified in versions prior to 4.5.4, where the default authentication secret is hardcoded, leading to potential unauthorized access to sensitive environment variables.
Vulnerability Detail
The vulnerability arises from three main issues: 1) A hardcoded default authentication secret ('coordinator-secret') that is publicly accessible in the source code, making it easy for attackers to exploit. 2) The 'READY_FOR_EXECUTION' handler allows any authenticated user to retrieve decrypted environment variables of any run, exposing sensitive data. 3) Other handlers permit unauthorized write operations against arbitrary runs, allowing attackers to manipulate tasks without proper authorization. This combination of flaws can lead to severe data breaches, as attackers can exfiltrate sensitive information and disrupt operations.
How To Fix
Latest published version: 4.7.7 as of 22 Oct 2026
npm install trigger.dev@4.7.7Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
4.5.4
This is the first release that contains the fix.
npm install trigger.dev@4.5.4Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary measure, operators should ensure that their self-hosted instances are not accessible from the public internet until they can upgrade to the patched version. Additionally, they should review their configurations to ensure that no default secrets are being used.
Conclusion
The identified vulnerabilities in Trigger.dev pose significant risks to self-hosted instances, allowing unauthorized access to sensitive data. Upgrading to version 4.5.4 or later is essential to mitigate these risks. Operators should also consider using tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for trigger.dev →
FAQ
The vulnerability involves hardcoded default authentication secrets and the ability for authenticated users to access sensitive environment variables.
You can use Vulert, which monitors open-source vulnerabilities in real-time. By checking your package-lock.json file, you can identify if your application is affected by this vulnerability.
Attackers can exfiltrate sensitive environment variables, leading to data breaches and unauthorized access to critical services.
Yes, ensure that your self-hosted instance is not publicly accessible and review your configurations to avoid using default secrets.
The CVSS score of this vulnerability is 9.2, indicating a critical level of severity.
References
Related vulnerabilities
Recent vulnerabilities recorded for trigger.dev.
