Quick answers
- Is CVE-2026-114078 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114078 being exploited in the wild.
- How severe is CVE-2026-114078?
- High severity, with a CVSS score of 8.1, published 21 October 2026.
- Which products and versions are affected?
- Trigger.dev before 4.5.6.
- Is there a fix for CVE-2026-114078?
- 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-114078 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-114078?
- 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 DeleteTaskScheduleService and SetActiveOnTaskScheduleService validate that a caller belongs to their own project, but then look up the target schedule by friendlyId alone without scoping to the caller's organization or project. An authenticated network attacker can send requests through their own project's route with a victim schedule's friendlyId to delete or disable IMPERATIVE cron schedules in other organizations; DECLARATIVE schedules are rejected. The fix ensures schedule lookups include projectId scope matching the caller's accessible project.
Affected products
- Trigger.dev trigger.dev before 4.5.6
Timeline
- 2026-07-21: disclosed
- 2026-10-20: advisory: VulnCheck advisory published
- 2026-10-21: patched: Published date suggests patch available