Skip to content
High-Priority SQL Injection Vulnerability in trigger.dev Exposes Tenant Data

High-Priority SQL Injection Vulnerability in trigger.dev Exposes Tenant Data

First seen 22 Oct 2026, 01:09 UTC • •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 22, 2026 at 01:38 UTC
  • •CVE-2026-114081 allows SQL injection in trigger.dev versions before 4.5.6.
  • •Authenticated users can access other tenants' analytics data via crafted queries.
  • •Immediate upgrade to version 4.5.6 is recommended to mitigate risks.

A SQL injection vulnerability, CVE-2026-114081, was disclosed for trigger.dev versions prior to 4.5.6. This flaw allows authenticated users to execute queries that can exfiltrate analytics data from other tenants due to inadequate input sanitization in the TSQL query compiler. Attackers can exploit this vulnerability by submitting crafted queries to the POST /api/v1/query endpoint, potentially accessing sensitive data from multiple organizations. The risk is particularly high for internet-accessible, multi-tenant analytics deployments. No active exploitation has been reported yet, but the vulnerability poses significant confidentiality risks. Users are advised to upgrade to the fixed version immediately and restrict access to the query endpoint until patched. The CVSS score for this vulnerability is 8.3, indicating a high severity level.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-21
CVE-2026-114081 published
trigger.dev disclosed an SQL injection vulnerability affecting versions prior to 4.5.6.
Redpacketsecurity
2026-10-22
Security advisory released
GitHub published a security advisory detailing the SQL injection vulnerability and its impact.
github.com

More articles in this cluster (2)

Following this threat?

Track CVE-2026-114081 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Extracted Entities (6)

1 / 4

Common questions

What versions are affected?
trigger.dev versions prior to 4.5.6 are affected by this vulnerability.
Is there any active exploitation reported?
No active exploitation has been reported as of now.
What should I do to protect my system?
Upgrade to trigger.dev version 4.5.6 immediately and restrict access to the query endpoint until patched.