CVE Alert: CVE-2026-114081 – triggerdotdev

Trigger.dev before 4.5.6 contains an SQL injection vulnerability in the TSQL query compiler, which concatenates window-function names into generated ClickHouse SQL without allowlisting or escaping. Authenticated customers can submit a backtick-quoted identifier to POST /api/v1/query that injects a raw subquery outside the per-tenant WHERE guard, exfiltrating other organizations’ analytics data.

**Risk verdict:** Treat this as a high-priority confidentiality risk wherever affected deployments are reachable by customer accounts; no active-exploitation or probability indicators were supplied to refine urgency.

**Why this matters:** A low-privilege account may be able to read analytics belonging to other organisations, creating material privacy, contractual and regulatory exposure. Likely attacker goals include harvesting customer data for resale, targeted fraud or intelligence gathering; integrity and availability impacts appear less central.

**Most likely attack path:** An attacker needs network access and a valid account, but no further conditions or victim interaction are indicated. Crafted query input may cross tenant boundaries, so compromise of one customer account could expose data held for others.

**Who is most exposed:** Prioritise internet-accessible, multi-tenant analytics deployments, especially those accepting customer-generated queries. Self-hosted instances may also be at risk if they expose the affected endpoint to untrusted users.

Review query-endpoint logs for unusual window-function names, backticks or embedded query syntax.

Look for requests followed by unusually broad or cross-tenant result sets.

Correlate suspicious queries with account, tenant and source-IP activity.

Check for unexpected bulk exports or analytics access across tenant boundaries.

Mitigation and prioritisation:

Upgrade to the vendor’s fixed release promptly; verify the deployed build rather than relying on package intent.

Until patched, restrict query-endpoint access to trusted users and consider disabling it.

Enforce tenant scoping server-side and monitor or rate-limit query activity.

Preserve relevant logs and investigate potential cross-tenant data access; schedule deployment with regression testing.

Confirm KEV, SSVC, EPSS and PoC status, which were not provided.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.