Is CVE-2026-114065 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114065 being exploited in the wild.

How severe is CVE-2026-114065?

Medium severity, with a CVSS score of 6.5, published 21 October 2026.

Is there a fix for CVE-2026-114065?

Yes: fixed in 4.7.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114065 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-114065?

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.

CVE-2026-114065: Trigger.dev tenant filtering bypass in query endpoint

CVE-2026-114065 · Severity: medium · CVSS 6.5 · Published 2026-10-21

Trigger.dev is a workflow automation platform that handles sensitive run metadata and payloads across multiple customer tenants. An authenticated attacker can use specially crafted SQL queries to read data belonging to other tenants, exposing confidential information like workflow runs and their associated payloads. The vulnerability requires network access and valid authentication, but does not allow data modification.

Technologies: Trigger.dev. Vendors: Trigger.dev.

Quick answers

Is CVE-2026-114065 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114065 being exploited in the wild.
How severe is CVE-2026-114065?: Medium severity, with a CVSS score of 6.5, published 21 October 2026.
Which products and versions are affected?: Trigger.dev before 4.7.3.
Is there a fix for CVE-2026-114065?: Yes: fixed in 4.7.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114065 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-114065?: 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.7.3

Technical details

A tenant filtering bypass in the POST /api/v1/query endpoint allows authenticated users to bypass table allowlists and tenant filters by using placeholder table syntax (FROM {database.table}) in queries, including within subqueries. The query compiler failed to apply organization, project, and environment predicates to placeholder expressions, instead emitting them as unfiltered physical table references. This enables SQL injection-like behavior that exposes other tenants' accessible data.

Affected products

Trigger.dev trigger.dev before 4.7.3

Timeline

2026-10-06: disclosed
2026-10-20: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.