# CVE-2026-114068: Trigger.dev missing authorization in waitpoint token endpoint

Source: https://junglewise.ai/threats/cve-2026-114068-trigger-dev-before-4-6-0-contains-a-missing-authorization  
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-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](https://junglewise.ai/threats/technologies/trigger-dev). Vendors: [Trigger.dev](https://junglewise.ai/threats/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

- [https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-xrp6-5fpv-4fxf](https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-xrp6-5fpv-4fxf)
- [https://www.vulncheck.com/advisories/trigger-dev-before-4.6.0-missing-authorization-via-waitpoint-token-wait-endpoint](https://www.vulncheck.com/advisories/trigger-dev-before-4.6.0-missing-authorization-via-waitpoint-token-wait-endpoint)

## 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)