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