CVE-2026-114084 triggerdotdev CVE debrief

Who should care

Defenders responsible for Trigger.dev instances, especially those with self-hosted deployments, should assess exposure and prioritize remediation. This involves verifying instance versions and updating to 4.5.6 or later.

Why it matters

The SQL injection vulnerability in Trigger.dev before 4.5.6 allows authenticated attackers to stream TaskRun records from every organization on the same self-hosted instance. Defenders should prioritize verifying exposure and remediating vulnerable instances.

• Potential unauthorized data access through TaskRun records
• Possible disruption of service through manipulation of TaskRun records
• Need for verification of instance version and exposure
• Priority on updating to patched version 4.5.6 or later

Technical summary

The SQL injection vulnerability in Trigger.dev before 4.5.6 is located in the /realtime/v1/runs endpoint. An authenticated attacker with a project API key holding the read:runs scope can exploit this vulnerability by appending boolean conditions to the tags query parameter. This allows the attacker to stream TaskRun records, including payloads and metadata, from every organization on the same self-hosted instance.

Defensive priority

Defenders should prioritize verifying exposure and remediating vulnerable instances of Trigger.dev, especially those with self-hosted deployments. This involves checking for instances running versions prior to 4.5.6 and updating to the patched version.

Recommended defensive actions

• Verify Trigger.dev instance version and update to 4.5.6 or later if necessary
• Restrict API key access to minimize scope of potential exploitation
• Monitor /realtime/v1/runs endpoint for suspicious activity
• 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 SQL injection vulnerability in Trigger.dev before 4.5.6. The vulnerability is in the /realtime/v1/runs endpoint and allows authenticated attackers to append boolean conditions to stream TaskRun records.

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.