CVE-2026-73655
Trigger.dev is a platform for building and deploying fully managed …
Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. Prior to 4.5.2, addGoogleStrategy() in apps/webapp/app/services/googleAuth.server.ts passes a Google profile email to findOrCreateGoogleUser() in apps/webapp/app/models/user.server.ts without requiring Google's email_verified assertion. When existingEmailUser && !existingUser is true, the flow writes the new Google authIdentifier into the existing email-matched account and returns that user object, allowing an attacker-controlled Google profile with an unverified matching email to take over the account. This issue is fixed in version 4.5.2.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/triggerdotdev/trigger.dev/commit/34b1a181c2a1d33a53ebab88f84b05f81fea4254
- github.com/triggerdotdev/trigger.dev/pull/4199
- github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.2
- github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-rp8c-h4xr-w9qv
- nvd.nist.gov/vuln/detail/CVE-2026-73655
- cve.org/CVERecord?id=CVE-2026-73655
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.