# CVE-2026-73656: Trigger.dev: Cross-project deployment worker registration can modify another project's deployment state

> Attackers with valid API keys can modify other projects' deployment states by linking unauthorized background workers due to missing environment checks.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-j6vv-pq9h-f4wj

## What is CVE-2026-73656?

CVE-2026-73656 is a critical missing authorization vulnerability in triggerdotdev trigger.dev, published on 13 Aug 2026. Any signed-in user can exploit it over the network, 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.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.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-73656?


## How do I fix CVE-2026-73656?

No fix has been published for CVE-2026-73656 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73656 being exploited?

There is no known exploitation of CVE-2026-73656 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73656 and fix it if it is affected.

What it is: CVE-2026-73656 is a critical missing authorization vulnerability in triggerdotdev trigger.dev, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73656 in the wild and no public exploit code.

Affected product: triggerdotdev trigger.dev. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73656/ (Markdown: https://insights.sbomify.com/CVE-2026-73656/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73656
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73656
- OSV: https://osv.dev/vulnerability/CVE-2026-73656

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73656/
Summaries are generated and may contain mistakes; the official description above is the record.