CVE-2026-73656

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% 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
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: None knownExposed: 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.6, POST /api/v1/deployments/:deploymentId/background-workers calls CreateDeploymentBackgroundWorkerServiceV4.call() in apps/webapp/app/v3/services/createDeploymentBackgroundWorkerV4.server.ts, where workerDeployment.findFirst() selects a deployment by friendlyId without an environmentId predicate. A caller with a valid API key for one project can submit another project's deployment identifier, link an attacker-owned background worker to the victim deployment, and move the victim deployment from BUILDING to DEPLOYING. This issue is fixed in version 4.5.6.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
45(Track)
EG Risk 45/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
Severity99% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 14, 2026

Advisory Details (4)

Auto-updated Aug 21, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Cross-project deployment worker registration can modify another project's deployment state · Advisory · triggerdotdev/trigger.dev · GitHub

https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-j6vv-pq9h-f4wj
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_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_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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 33× 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-27 19:32 UTCEG score recompute
  2. 2026-08-27 14:25 UTCEPSS rescore
  3. 2026-08-26 16:27 UTCEG score recompute
  4. 2026-08-26 14:47 UTCEPSS rescore
  5. 2026-08-25 15:02 UTCEG score recompute
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-24 14:29 UTCEG score recompute
  8. 2026-08-24 10:23 UTCEG score recompute
  9. 2026-08-23 01:32 UTCEG score recompute
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 00:57 UTCEG score recompute
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 00:22 UTCEG score recompute
  14. 2026-08-20 22:56 UTCEPSS rescore
  15. 2026-08-19 19:44 UTCEG score recompute
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-18 14:59 UTCEG score recompute
  18. 2026-08-18 13:49 UTCEPSS rescore
  19. 2026-08-18 13:49 UTCEPSS rescore
  20. 2026-08-17 17:05 UTCEG score recompute
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-16 16:33 UTCEG score recompute
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 04:18 UTCEG score recompute
Show 8 more
  1. 2026-08-16 02:15 UTCEPSS rescore
  2. 2026-08-15 03:47 UTCEG score recompute
  3. 2026-08-15 01:31 UTCEPSS rescore
  4. 2026-08-14 19:36 UTCEG score recompute
  5. 2026-08-14 18:34 UTCEG score recompute
  6. 2026-08-13 20:20 UTCEG score recompute
  7. 2026-08-13 20:02 UTCEG score recompute
  8. 2026-08-13 20:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73656?
CVE-2026-73656 is a critical 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.6, POST /api/v1/deployments/:deploymentId/background-workers calls CreateDeploymentBackgroundWorkerServiceV4.call() in apps/webapp/app/v3/services/createDeploymentBackgroundWorkerV4.server.ts,…
When was CVE-2026-73656 disclosed?
CVE-2026-73656 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73656 actively exploited?
CVE-2026-73656 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 73.1% of all scored CVEs.
What is the CVSS score of CVE-2026-73656?
CVE-2026-73656 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-73656?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73656, 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-73656

Explore →

Is Your Infrastructure Affected by CVE-2026-73656?

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