# Trigger.dev cross-tenant SQL injection in TSQL query compiler

Source: https://junglewise.ai/threats/trigger-dev-cross-tenant-sql-injection-in-the-tsql-query-compiler-post-98af5ddc  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-02. Updated: 2026-10-02  
License: CC BY 4.0 with a link back

Severity: high · CVSS 7.7 · Published 2026-10-02

Trigger.dev is an open-source platform that lets customers run and monitor automated workflows. A flaw in its SQL query compiler allows any authenticated customer to craft a malicious query that bypasses tenant isolation and reads other customers' data from the analytics database, including sensitive information like API keys and passwords.

Technologies: [trigger.dev (npm)](https://junglewise.ai/threats/technologies/npm-trigger-dev), [Trigger.dev](https://junglewise.ai/threats/technologies/trigger-dev). Vendors: [npm](https://junglewise.ai/threats/vendors/npm), [Trigger.dev](https://junglewise.ai/threats/vendors/trigger-dev).

## Quick answers

**Is This vulnerability exploited in the wild?** No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

**How severe is This vulnerability?** High severity, with a CVSS score of 7.7, published 2 October 2026.

**Which products and versions are affected?** trigger.dev (npm) <= 4.5.5; Trigger.dev prior to remediation.

**Is there a fix for This vulnerability?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is This vulnerability attacked?** It is attacked over the network, in a software library.

**Am I affected?** Check whether you run trigger.dev (npm) or Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The TSQL-to-ClickHouse compiler in internal-packages/tsql fails to sanitize or allowlist window function names at printer.ts:3073-3075, concatenating node.name directly into the SQL output. An attacker can inject a backtick-quoted identifier containing arbitrary SQL (e.g., a subquery targeting another organization) that escapes the per-tenant WHERE guard and executes unparameterized. The vulnerability requires only authentication as any customer via API key or JWT; the tenant authorization check only validates the outer FROM table, leaving the injected subquery in the SELECT position invisible and unguarded.

## Affected products

- Trigger.dev Trigger.dev prior to remediation

## Timeline

- 2026-10-02: disclosed: Published on GitHub Security Advisory

## Related threats

- [Trigger.dev cross-site request forgery in logout endpoint](https://junglewise.ai/threats/cve-2026-114093-trigger-dev-before-4-5-6-contains-a-cross-site-request-forgery)
- [Trigger.dev missing authentication in task run replay](https://junglewise.ai/threats/cve-2026-114092-trigger-dev-before-4-5-0-performs-no-authentication-or)
- [Trigger.dev cross-tenant authorization bypass in run replay](https://junglewise.ai/threats/cve-2026-114091-trigger-dev-before-4-5-0-looks-up-runs-by-friendlyid-alone-in)
- [Trigger.dev cross-site request forgery in CLI authorization flow](https://junglewise.ai/threats/cve-2026-114089-trigger-dev-before-4-5-2-contains-a-cross-site-request-forgery)
- [Trigger.dev hardcoded default secret authentication bypass in Socket.IO](https://junglewise.ai/threats/cve-2026-114088-trigger-dev-before-4-5-4-contains-a-hardcoded-default-secret)