CVE-2026-73655 Trigger.dev: Account Takeover via Cross-Provider OAuth Email Matching in Google Login
Attackers can take over accounts by using unverified Google emails that match existing users, bypassing authentication checks in Trigger.dev.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-73655?
CVE-2026-73655 is a high-severity authentication bypass vulnerability in triggerdotdev trigger.dev, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-287
Which versions are affected by CVE-2026-73655?
How do I fix CVE-2026-73655?
No fix has been published for CVE-2026-73655 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-73655 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73655 exists.
Sources
Also known as GHSA-rp8c-h4xr-w9qv.