Is CVE-2026-114079 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114079 being exploited in the wild.

How severe is CVE-2026-114079?

Medium severity, with a CVSS score of 5.4, published 21 October 2026.

Is there a fix for CVE-2026-114079?

Yes: fixed in Trigger.dev 4.5.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114079 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-114079?

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.

CVE-2026-114079: Trigger.dev authorization bypass in deployment cancellation

CVE-2026-114079 · Severity: medium · CVSS 5.4 · Published 2026-10-21

Trigger.dev is a platform for managing automated deployments and workflows across multiple environments (dev, staging, production). An attacker holding a lower-trust API key for development or preview environments can cancel production deployments in the same project without permission, causing service disruptions. This occurs because the deployment cancellation endpoint does not verify the environment matches the authenticated key, unlike the read endpoint which correctly enforces this restriction.

Technologies: Trigger.dev. Vendors: Trigger.dev.

Quick answers

Is CVE-2026-114079 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114079 being exploited in the wild.
How severe is CVE-2026-114079?: Medium severity, with a CVSS score of 5.4, published 21 October 2026.
Which products and versions are affected?: Trigger.dev before 4.5.6.
Is there a fix for CVE-2026-114079?: Yes: fixed in Trigger.dev 4.5.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114079 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-114079?: 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: Trigger.dev 4.5.6

Technical details

The vulnerability is an authorization bypass (CWE-639) in the DeploymentService.getDeployment() method, which scopes deployment lookups by projectId only and omits environmentId validation. An authenticated user with a dev, preview, or CI environment API key can POST to the deployment cancel endpoint and cancel in-progress deployments (PENDING, INSTALLING, BUILDING, DEPLOYING states) in any environment of the same project, including production. The deployment GET route correctly enforces environment scoping, creating an asymmetric authorization flaw.

Affected products

Trigger.dev Trigger.dev before 4.5.6

Timeline

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

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.