Trigger.dev: Cross-tenant SQL injection
Affects trigger.devSource GCVE Database
CVSS 7.7 High : upgrade to 4.5.6 soon.
Data as of 3 Oct 2026, 17:40 UTC
- Patch
- Available – fixed in 4.5.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NWhat to do
Upgrade trigger.dev to 4.5.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmtrigger.dev | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability. Users should apply the official fix provided by trigger.dev to ensure the window-function name is properly validated or escaped to prevent injection. Until patched, avoid using the vulnerable query endpoint or restrict access to trusted users only. Check the vendor advisory for the latest remediation guidance.
Description
A cross-tenant SQL injection vulnerability exists in trigger.dev's TSQL query compiler at the POST /api/v1/query endpoint. The vulnerability arises because the window-function name in the query is concatenated into the SQL string without allowlisting or escaping, allowing an authenticated customer to inject raw subqueries that bypass tenant isolation. This enables an attacker to read analytics data belonging to other tenants. The issue has been verified end-to-end against the real compiler and a live ClickHouse database.
References
- github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-9q4r-4842-93vw (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/pull/4316 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/commit/6997aeb05e27d2db47f9eda01fdc8a17c81a1ae0 (opens in a new tab)
- github.com/triggerdotdev/trigger.dev (opens in a new tab)
- github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.6 (opens in a new tab)