CVE-2026-114089: Trigger.dev cross-site request forgery in CLI authorization flow

CVE-2026-114089 · Severity: high · CVSS 8.8 · Published 2026-10-21

Trigger.dev is a platform for building and managing event-driven workflows. A cross-site request forgery vulnerability in its CLI authorization flow allows attackers to trick logged-in users into unknowingly granting access tokens. An attacker can use these tokens to take over user accounts, delete organizations, rotate API keys, and invite themselves as members to access sensitive data and configurations.

Technologies: Trigger.dev. Vendors: Trigger.dev.

Quick answers

Is CVE-2026-114089 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-114089 being exploited in the wild.
How severe is CVE-2026-114089?
High severity, with a CVSS score of 8.8, published 21 October 2026.
Which products and versions are affected?
Trigger.dev before 4.5.2.
Is there a fix for CVE-2026-114089?
Yes: fixed in 4.5.2. Until then: Restrict access to the /account/authorization-code endpoint and /api/v1/token endpoint through network policies or rate limiting until patched. Require MFA for all user accounts to add an additional barrier to account takeover. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114089 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-114089?
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.2

Restrict access to the /account/authorization-code endpoint and /api/v1/token endpoint through network policies or rate limiting until patched. Require MFA for all user accounts to add an additional barrier to account takeover.

Technical details

The vulnerability exists in the authorization-code-to-PAT flow where GET /account/authorization-code/<code> mints a Personal Access Token without a consent step or user confirmation. An attacker can obtain an unauthenticated code via POST /api/v1/authorization-code, lure a logged-in victim to click the authorization URL, and then retrieve the plaintext PAT from the unauthenticated POST /api/v1/token endpoint. The flow lacks rate limiting and MFA step-up, combined with insufficient role-based access controls allowing any organization member to perform destructive actions.

Affected products

  • Trigger.dev Trigger.dev before 4.5.2

Timeline

  • 2026-07-09: disclosed
  • 2026-10-21: advisory
  • 2026-10-21: patched: Version 4.5.2 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.