CVE-2026-73655

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
49(Track*)
EG Risk 49/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 18, 2026

Advisory Details (4)

Auto-updated Aug 13, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

trigger.dev v4.5.2

Patch available: triggerdotdev/trigger.dev v4.5.2

https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.2
github_commit Patch Available

commit 34b1a181c2a1 (triggerdotdev/trigger.dev)

Patch available: triggerdotdev/trigger.dev v4.5.2 (contains commit 34b1a181c2a1)

https://github.com/triggerdotdev/trigger.dev/commit/34b1a181c2a1d33a53ebab88f84b05f81fea4254
github_pr Patch Available

fix: security release 2026-07-06

Patch available: triggerdotdev/trigger.dev v4.5.2 (PR #4199 merged 2026-07-09)

https://github.com/triggerdotdev/trigger.dev/pull/4199
github Patch Available🟡 PoC Available

Account Takeover via Cross-Provider OAuth Email Matching in Google Login · Advisory · triggerdotdev/trigger.dev · GitHub

https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-rp8c-h4xr-w9qv

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 07:13 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 22:52 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 22:01 UTCEG score recompute
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-25 21:04 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 20:13 UTCEG score recompute
  11. 2026-08-23 06:55 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 06:05 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 05:13 UTCEG score recompute
  16. 2026-08-20 22:56 UTCEPSS rescore
  17. 2026-08-20 04:23 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 14:59 UTCEG score recompute
  20. 2026-08-18 13:49 UTCEPSS rescore
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 02:20 UTCEG score recompute
  23. 2026-08-18 01:47 UTCEG score recompute
  24. 2026-08-17 23:45 UTCEG score recompute
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 10 more
  1. 2026-08-16 22:54 UTCEG score recompute
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 10:28 UTCEG score recompute
  5. 2026-08-16 02:15 UTCEPSS rescore
  6. 2026-08-15 09:37 UTCEG score recompute
  7. 2026-08-15 01:31 UTCEPSS rescore
  8. 2026-08-13 20:20 UTCEG score recompute
  9. 2026-08-13 20:02 UTCEG score recompute
  10. 2026-08-13 20:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73655?
CVE-2026-73655 is a high vulnerability published on August 13, 2026. 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…
When was CVE-2026-73655 disclosed?
CVE-2026-73655 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73655 actively exploited?
CVE-2026-73655 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.0% of all scored CVEs.
What is the CVSS score of CVE-2026-73655?
CVE-2026-73655 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-73655?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73655, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73655

Explore →

Is Your Infrastructure Affected by CVE-2026-73655?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs