CVE-2026-114084: Trigger.dev before 4.5.6 SQL Injection via tags in Realtime Runs API

Q: Who can exploit this issue?

An attacker needs a valid project API key with the read:runs scope. The issue affects self-hosted instances, where such an authenticated user can access data across organizations on the same instance.

Q: What data could be exposed?

An attacker can inject boolean conditions through the tags query parameter to bypass the runtimeEnvironmentId tenant guard. This can allow streaming of TaskRun records, including their payloads and metadata, from every organization on the instance.

Q: Which endpoint and input should be investigated for exploitation attempts?

Review requests to the /realtime/v1/runs endpoint, particularly the tags query parameter. Injection attempts would use that parameter to alter the ElectricSQL shape where clause.

Q: What version resolves the issue?

Upgrade Trigger.dev to version 4.5.6 or later. Versions before 4.5.6 are affected.

Published Oct 21, 2026

Updated

Trigger.dev before 4.5.6 contains an SQL injection vulnerability in the /realtime/v1/runs endpoint, which concatenates the unescaped tags query parameter into the ElectricSQL shape where clause and defeats the runtimeEnvironmentId tenant guard. Authenticated attackers holding any project API key with read:runs scope can append boolean conditions to stream TaskRun records, including payloads and metadata, from every organization on the same self-hosted instance.

Affected Software

1 affected component

Trigger.dev Trigger.dev<4.5.6

Event History

Oct 21, 2026

CVE Published

via MITRE·12:36 AM

Data Sourced

via MITRE·12:36 AM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

An attacker needs a valid project API key with the read:runs scope. The issue affects self-hosted instances, where such an authenticated user can access data across organizations on the same instance.

What data could be exposed?

An attacker can inject boolean conditions through the tags query parameter to bypass the runtimeEnvironmentId tenant guard. This can allow streaming of TaskRun records, including their payloads and metadata, from every organization on the instance.

Which endpoint and input should be investigated for exploitation attempts?

Review requests to the /realtime/v1/runs endpoint, particularly the tags query parameter. Injection attempts would use that parameter to alter the ElectricSQL shape where clause.

What version resolves the issue?

Upgrade Trigger.dev to version 4.5.6 or later. Versions before 4.5.6 are affected.

CVE-2026-114084: Trigger.dev before 4.5.6 SQL Injection via tags in Realtime Runs API

Affected Software

Event History

Frequently Asked Questions

Who can exploit this issue?

What data could be exposed?

Which endpoint and input should be investigated for exploitation attempts?

What version resolves the issue?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

What data could be exposed?

Which endpoint and input should be investigated for exploitation attempts?

What version resolves the issue?