CVE-2026-114089 triggerdotdev CVE debrief

Who should care

Defenders responsible for Trigger.dev installations, security teams, and developers using Trigger.dev should assess exposure and prioritize upgrading to version 4.5.2 or later. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Defenders should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

CVE-2026-114089 is a high-severity vulnerability in Trigger.dev before 4.5.2 that allows for cross-site request forgery in the CLI authorization-code flow, potentially leading to PAT takeover. Defenders should prioritize verifying exposure and upgrading to version 4.5.2 or later.

• Potential takeover of accounts through PAT
• Exposure to phishing attacks through CLI authorization-code flow
• Need for verification of Trigger.dev installations and user accounts
• Priority on upgrading to version 4.5.2 or later

Technical summary

Trigger.dev before 4.5.2 contains a cross-site request forgery vulnerability in the CLI authorization-code flow. This allows attackers to mint an unauthenticated code, lure a logged-in user to that URL, and then retrieve the victim's Personal Access Token (PAT) from the unauthenticated /api/v1/token endpoint to take over the account. The vulnerability has a high CVSS score of 8.7, indicating a high severity. The affected product is Trigger.dev, and the vulnerability is related to the CLI authorization-code flow. Defenders should prioritize verifying exposure and upgrading to version 4.5.2 or later.

Defensive priority

Defenders should prioritize verifying exposure of Trigger.dev installations and upgrading to version 4.5.2 or later.

Recommended defensive actions

• Verify Trigger.dev installations for exposure to the CLI authorization-code flow vulnerability
• Upgrade Trigger.dev to version 4.5.2 or later
• Monitor for potential phishing attempts targeting Trigger.dev users
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, CVSS score, and affected versions. The vulnerability was reported by an external researcher and verified by the vendor. The CVE record was published on 2026-10-21T00:36:54.860Z and has not been modified since then. There are no known exploits in the wild, but defenders should prioritize verifying exposure and upgrading to version 4.5.2 or later. The vendor has released a patch for the vulnerability, and defenders should apply it as soon as

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.