Trigger.dev before version 4.7.3 permits a tenant filtering bypass that lets an authenticated user read data belonging to other tenants by crafting SQL queries using placeholder table syntax. The flaw allows insertion of FROM {database.table} expressions, even within subqueries, which defeats the table allowlist and tenant filters. This effectively enables a remote user to retrieve run metadata and payload contents from other tenants, representing a breach of confidentiality and an injection-based weakness, identified as CWE-89.

Adsorbing the information available, the vulnerability exists in the Trigger.dev platform in all releases prior to version 4.7.3. The impacted entity is Trigger.dev, and the affected product is the official Trigger.dev service. Precise version data is best described as "ending with 4.7.3"; any instance released before that must apply a fix.

The CVSS score of 7.1 signals a high impact, yet the EPSS score of less than 1% indicates that exploitation is unlikely to be widespread at present. The vulnerability is not listed under CISA’s KEV catalog. Attackers need only an authenticated session with a user account that can submit queries through the POST /api/v1/query endpoint. In that context, the authentication requirement makes the attack less trivial than a fully unauthenticated vulnerability, but once a legitimate session is in place, an attacker can craft malicious queries to bypass tenant isolation and read other tenants' data.