CVE-2026-114084: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in triggerdotdev trigger.dev
Description
Trigger.dev versions before 4.5.6 have an SQL injection vulnerability in the /realtime/v1/runs endpoint. This flaw allows authenticated attackers with any project API key having read:runs scope to manipulate the tags query parameter, bypassing tenant isolation and accessing TaskRun records, including payloads and metadata, across all organizations on the same self-hosted instance.
CVSS v4.0
Score 8.3high
Affected software
triggerdotdev
trigger.dev
pkg:github/triggerdotdev/trigger.devRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Trigger.dev prior to version 4.5.6 contains an SQL injection vulnerability in the /realtime/v1/runs endpoint. The vulnerability arises because the tags query parameter is concatenated without proper escaping into the ElectricSQL shape where clause, which also defeats the runtimeEnvironmentId tenant guard. This allows authenticated attackers holding any project API key with read:runs scope to append boolean conditions to stream TaskRun records from every organization on the same self-hosted instance, potentially exposing sensitive payloads and metadata.
Potential Impact
An attacker with a valid project API key and read:runs scope can exploit this vulnerability to bypass tenant isolation and access TaskRun records, including sensitive payloads and metadata, from all organizations hosted on the same self-hosted Trigger.dev instance. This could lead to unauthorized data disclosure across tenant boundaries.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects self-hosted instances, administrators should monitor vendor communications for an official fix and apply it promptly once available. Until then, restrict API key permissions and consider limiting access to trusted users only.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-10-20T21:46:05.992Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ad80c062cdf04f6568caa40
Added to database: 10/21/2026, 00:49:10 UTC
Last enriched: 10/21/2026, 01:18:47 UTC
Last updated: 10/21/2026, 01:48:24 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.