{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73655 exists.","fix":"No fix has been published for CVE-2026-73655 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-73655 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73655 exists.\n\nAffected product: triggerdotdev trigger.dev. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-73655/ (Markdown: https://insights.sbomify.com/CVE-2026-73655/index.md)","id":"CVE-2026-73655","markdown":"https://insights.sbomify.com/CVE-2026-73655/index.md","name":"CVE-2026-73655","record":{"aliases":["GHSA-rp8c-h4xr-w9qv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"AI agent platform","requires_auth":"none","summary":"Attackers can take over accounts by using unverified Google emails that match existing users, bypassing authentication checks in Trigger.dev.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"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 \u0026\u0026 !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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Trigger.dev: Account Takeover via Cross-Provider OAuth Email Matching in Google Login","id":"CVE-2026-73655","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Trigger.dev: Cross-project deployment worker registration can modify another project's deployment state","id":"CVE-2026-73656"},"packages":[],"prev":{"headline":"Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant DoS","id":"CVE-2026-73654"},"products":["trigger.dev"],"published":"2026-08-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["triggerdotdev"]},"summary":"Attackers can take over accounts by using unverified Google emails that match existing users, bypassing authentication checks in Trigger.dev.","url":"https://insights.sbomify.com/CVE-2026-73655/"}