# CVE-2026-114077: Trigger.dev authorization bypass in createDeploymentBackgroundWorkerV4

Source: https://junglewise.ai/threats/cve-2026-114077-trigger-dev-before-4-5-6-contains-an-authorization-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-21. Updated: 2026-10-21  
License: CC BY 4.0 with a link back

CVE-2026-114077 · Severity: high · CVSS 7.1 · Published 2026-10-21

Trigger.dev is a workflow orchestration platform that manages deployment and execution of background workers. An attacker with their own API key can hijack another organization's in-progress deployment, redirecting it to run code in the attacker's environment and potentially exfiltrating data or disrupting service delivery for the victim organization.

Technologies: [Trigger.dev](https://junglewise.ai/threats/technologies/trigger-dev). Vendors: [Trigger.dev](https://junglewise.ai/threats/vendors/trigger-dev).

## Quick answers

**Is CVE-2026-114077 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-114077 being exploited in the wild.

**How severe is CVE-2026-114077?** High severity, with a CVSS score of 7.1, published 21 October 2026.

**Which products and versions are affected?** Trigger.dev before 4.5.6.

**Is there a fix for CVE-2026-114077?** Yes: fixed in 4.5.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-114077 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-114077?** Check whether you run Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 4.5.6

## Technical details

The createDeploymentBackgroundWorkerV4 endpoint resolves a WorkerDeployment using only the friendlyId parameter, without checking environment, project, or organization scope. An attacker with a valid API key for their own environment can POST a victim's deployment ID to this endpoint, causing the victim's BUILDING deployment to transition to DEPLOYING with a workerId pointing to the attacker's background worker, leaking version information and compromising deployment integrity.

## Affected products

- Trigger.dev Trigger.dev before 4.5.6

## Timeline

- 2026-07-21: disclosed
- 2026-10-21: advisory

## References

- [https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-2gvw-9968-v578](https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-2gvw-9968-v578)
- [https://www.vulncheck.com/advisories/trigger-dev-before-4.5.6-cross-tenant-deployment-hijack-via-createdeploymentbackgroundworkerv4](https://www.vulncheck.com/advisories/trigger-dev-before-4.5.6-cross-tenant-deployment-hijack-via-createdeploymentbackgroundworkerv4)

## Related threats

- [Trigger.dev cross-site request forgery in logout endpoint](https://junglewise.ai/threats/cve-2026-114093-trigger-dev-before-4-5-6-contains-a-cross-site-request-forgery)
- [Trigger.dev missing authentication in task run replay](https://junglewise.ai/threats/cve-2026-114092-trigger-dev-before-4-5-0-performs-no-authentication-or)
- [Trigger.dev cross-tenant authorization bypass in run replay](https://junglewise.ai/threats/cve-2026-114091-trigger-dev-before-4-5-0-looks-up-runs-by-friendlyid-alone-in)
- [Trigger.dev cross-site request forgery in CLI authorization flow](https://junglewise.ai/threats/cve-2026-114089-trigger-dev-before-4-5-2-contains-a-cross-site-request-forgery)
- [Trigger.dev hardcoded default secret authentication bypass in Socket.IO](https://junglewise.ai/threats/cve-2026-114088-trigger-dev-before-4-5-4-contains-a-hardcoded-default-secret)