# CVE-2026-114093: Trigger.dev cross-site request forgery in logout endpoint

Source: https://junglewise.ai/threats/cve-2026-114093-trigger-dev-before-4-5-6-contains-a-cross-site-request-forgery  
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-114093 · Severity: medium · CVSS 4.3 · Published 2026-10-21

Trigger.dev is a workflow automation platform used to manage background jobs and integrations. A cross-site request forgery (CSRF) vulnerability in the logout endpoint allows attackers to log out authenticated users by tricking them into clicking a malicious link, causing loss of unsaved work and session termination.

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

## References

- [https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-2cqj-rq4j-8835](https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-2cqj-rq4j-8835)
- [https://www.vulncheck.com/advisories/trigger-dev-before-4.5.6-cross-site-request-forgery-via-logout-endpoint](https://www.vulncheck.com/advisories/trigger-dev-before-4.5.6-cross-site-request-forgery-via-logout-endpoint)

## Related threats

- [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)
- [Trigger.dev authentication bypass via hardcoded secrets in Docker Compose](https://junglewise.ai/threats/cve-2026-114087-trigger-dev-before-4-5-6-self-hosted-docker-compose-deployments)