Is CVE-2026-114068 exploited in the wild?

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

How severe is CVE-2026-114068?

High severity, with a CVSS score of 8.3, published 21 October 2026.

Is there a fix for CVE-2026-114068?

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

How is CVE-2026-114068 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-114068?

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-114068: Trigger.dev missing authorization in waitpoint token endpoint

CVE-2026-114068 · Severity: high · CVSS 8.3 · Published 2026-10-21

Trigger.dev is a workflow automation platform that executes scheduled tasks and jobs. An authenticated attacker with any secret API key can block or suspend task runs belonging to other organizations by injecting a malicious waitpoint, causing those runs to hang indefinitely. An attacker can also inject data into suspended runs, potentially corrupting their execution state or leaking sensitive information.

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

Quick answers

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

Technical details

The waitpoint token wait endpoint (POST /engine/v1/runs/:runFriendlyId/waitpoints/tokens/:waitpointFriendlyId/wait) validates that the waitpoint belongs to the caller's environment but fails to verify that the run belongs to the same organization, allowing cross-tenant run suspension. An authenticated attacker holding a secret API key can supply an arbitrary victim run ID from another organization along with their own waitpoint to block that run indefinitely on a waitpoint it cannot see or complete. The vulnerability exists because the run ID is decoded directly from the URL without scope validation, whereas a sibling endpoint in the same codebase correctly performs this check before making the same engine call.

Affected products

Trigger.dev Trigger.dev before 4.6.0

Timeline

2026-10-21: disclosed
2026-09-14: advisory: GitHub Security Advisory GHSA-xrp6-5fpv-4fxf

References

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