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.