Quick answers
- Is CVE-2026-114081 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114081 being exploited in the wild.
- How severe is CVE-2026-114081?
- High severity, with a CVSS score of 7.7, published 21 October 2026.
- Which products and versions are affected?
- Trigger.dev before 4.5.6.
- Is there a fix for CVE-2026-114081?
- Yes: fixed in 4.5.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114081 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-114081?
- Check whether you run 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.
How to fix
- Fixed in: 4.5.6
Technical details
The vulnerability is a SQL injection in the TSQL query compiler (internal-packages/tsql/src/query/printer.ts) where window-function names are concatenated into ClickHouse SQL without allowlisting or escaping. An authenticated attacker submits a backtick-quoted identifier to POST /api/v1/query containing a malicious subquery (e.g., `(SELECT ... FROM task_runs_v2 WHERE organization_id = 'org_VICTIM')`) that executes outside the per-tenant WHERE guard enforced on the outer table, allowing cross-tenant data exfiltration. The attack requires valid API credentials and normal authorization checks do not block the injection since it resides in the SELECT/window position rather than the table FROM clause.
Affected products
- Trigger.dev Trigger.dev before 4.5.6
Timeline
- 2026-07-21: disclosed
- 2026-10-21: advisory