Quick answers
- Is CVE-2026-114066 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114066 being exploited in the wild.
- How severe is CVE-2026-114066?
- High severity, with a CVSS score of 8.1, published 21 October 2026.
- Which products and versions are affected?
- Trigger.dev before 4.7.0.
- Is there a fix for CVE-2026-114066?
- Yes: fixed in Trigger.dev 4.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114066 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-114066?
- 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.7.0
Technical details
The batch-creation endpoints (POST /api/v3/batches and POST /api/v2/tasks/batch) accept a caller-supplied parentRunId parameter but fail to verify that the parent run belongs to the caller's environment before creating a waitpoint against it. The authorization guard short-circuits for unrestricted API keys without confirming run ownership, allowing the attacker to suspend or inject errors into runs in other environments, projects, or organizations. The vulnerability is reachable only to authenticated API key holders but affects any run whose ID is known.
Affected products
- Trigger.dev Trigger.dev before 4.7.0
Timeline
- 2026-10-02: disclosed
- 2026-10-21: advisory
- 2026-10-21: patched