Quick answers
- Is CVE-2026-114093 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114093 being exploited in the wild.
- How severe is CVE-2026-114093?
- Medium severity, with a CVSS score of 4.3, published 21 October 2026.
- Which products and versions are affected?
- Trigger.dev before 4.5.6.
- Is there a fix for CVE-2026-114093?
- Yes: fixed in 4.5.6. Until then: Implement CSRF token validation on the logout endpoint and convert the endpoint from GET-based to POST-based request handling to prevent accidental session termination via link clicks. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114093 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-114093?
- 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
Implement CSRF token validation on the logout endpoint and convert the endpoint from GET-based to POST-based request handling to prevent accidental session termination via link clicks.
Technical details
The logout endpoint accepts GET requests without CSRF token validation, allowing an attacker to craft a URL (with obfuscation like URL encoding) that logs out a victim when clicked. No authentication or special privileges are required; only user interaction (clicking a link) is needed. The vulnerability results in availability impact through session loss and potential work loss, but does not expose data or compromise integrity.
Affected products
- Trigger.dev Trigger.dev before 4.5.6
Timeline
- 2026-07-21: disclosed
- 2026-10-20: advisory
- 2026-10-21: patched