CVE-2026-114066 triggerdotdev CVE debrief

Who should care

Defenders responsible for Trigger.dev deployments, particularly those using environment API keys, should assess exposure and prioritize upgrading to version 4.7.0 or later. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure, review batch-creation endpoint access, and monitor for potential unauthorized activity using environment API keys.

Why it matters

CVE-2026-114066 is a high-severity vulnerability in Trigger.dev before version 4.7.0, allowing unauthorized blocking or error injection into production or cross-organization runs using batch-creation endpoints. Defenders should prioritize verifying exposure and upgrading to version 4.7.0 or later.

• Potential disruption of critical workflows due to unauthorized blocking or error injection.
• Verification of exposure and potential impact on production or cross-organization runs.
• Prioritization of upgrading to version 4.7.0 or later to prevent unauthorized activity.
• Monitoring for potential unauthorized activity using environment API keys.

Technical summary

Trigger.dev before 4.7.0 contains a missing authorization vulnerability that allows holders of unrestricted environment API keys to block runs they do not own by supplying a foreign parentRunId to batch-creation endpoints. This vulnerability can lead to potential disruption of critical workflows due to unauthorized blocking or error injection into production or cross-organization runs. Defenders should prioritize verifying exposure and upgrading to version 4.7.0 or later to prevent unauthorized activity. The vulnerability is exploitable via POST /api/v3/batches or POST /api/v2/tasks/batch with resumeParentOnCompletion.

Defensive priority

Defenders should prioritize verifying exposure and upgrading to version 4.7.0 or later, as this vulnerability allows for potential disruption of critical workflows.

Recommended defensive actions

• Verify if Trigger.dev versions before 4.7.0 are in use and upgrade to 4.7.0 or later.
• Review and restrict access to batch-creation endpoints.
• Monitor for potential unauthorized activity using environment API keys.
• 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 vulnerability is described in the CVE Program record and NVD vulnerability detail page. The source item provides additional information on the affected versions and potential impact. Evidence is limited to public CVE Program records and NVD vulnerability details. Defenders should verify exposure using environment API key usage and review batch-creation endpoint access. Additional verification may be required to confirm affected scope and severity.

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.