CVE-2026-73656: CWE-639: Authorization Bypass Through User-Controlled Key in triggerdotdev trigger.dev
Trigger.dev versions prior to 4.5.6 contain an authorization bypass vulnerability in the background worker deployment API. The flaw allows a user with a valid API key for one project to manipulate another project's deployment by linking an attacker-owned background worker to the victim deployment and changing its state from BUILDING to DEPLOYING. This issue is addressed in version 4.5.6.
AI Analysis
Technical Summary
Trigger.dev's POST /api/v1/deployments/:deploymentId/background-workers endpoint calls CreateDeploymentBackgroundWorkerServiceV4.call(), which uses workerDeployment.findFirst() to select deployments by friendlyId without filtering by environmentId. This allows an attacker with a valid API key for one project to submit a deployment identifier from another project, effectively linking an attacker-controlled background worker to the victim deployment and altering its deployment state. The vulnerability is an authorization bypass related to improper access control (CWE-639 and CWE-862). It is fixed in version 4.5.6.
Potential Impact
An attacker with limited privileges (a valid API key for one project) can interfere with deployments of other projects by linking malicious background workers and changing deployment states. This can lead to unauthorized modification of deployment workflows, potentially impacting the integrity and availability of victim deployments. The CVSS score of 9.9 indicates critical severity with high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade to Trigger.dev version 4.5.6 or later, where this authorization bypass vulnerability has been fixed. No other mitigation steps are indicated by the vendor advisory.
CVE-2026-73656: CWE-639: Authorization Bypass Through User-Controlled Key in triggerdotdev trigger.dev
Description
Trigger.dev versions prior to 4.5.6 contain an authorization bypass vulnerability in the background worker deployment API. The flaw allows a user with a valid API key for one project to manipulate another project's deployment by linking an attacker-owned background worker to the victim deployment and changing its state from BUILDING to DEPLOYING. This issue is addressed in version 4.5.6.
CVSS v3.1
Score 9.9critical
Affected software
pkg:github/triggerdotdev/trigger.devRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Trigger.dev's POST /api/v1/deployments/:deploymentId/background-workers endpoint calls CreateDeploymentBackgroundWorkerServiceV4.call(), which uses workerDeployment.findFirst() to select deployments by friendlyId without filtering by environmentId. This allows an attacker with a valid API key for one project to submit a deployment identifier from another project, effectively linking an attacker-controlled background worker to the victim deployment and altering its deployment state. The vulnerability is an authorization bypass related to improper access control (CWE-639 and CWE-862). It is fixed in version 4.5.6.
Potential Impact
An attacker with limited privileges (a valid API key for one project) can interfere with deployments of other projects by linking malicious background workers and changing deployment states. This can lead to unauthorized modification of deployment workflows, potentially impacting the integrity and availability of victim deployments. The CVSS score of 9.9 indicates critical severity with high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade to Trigger.dev version 4.5.6 or later, where this authorization bypass vulnerability has been fixed. No other mitigation steps are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-13T14:04:09.605Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7e2504bf8831d539bed850
Added to database: 08/13/2026, 20:11:48 UTC
Last enriched: 08/13/2026, 20:26:07 UTC
Last updated: 08/13/2026, 20:36:50 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.