Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-9q4r-4842-93vw

Trigger.dev: Cross-tenant SQL injection in the TSQL query compiler (POST /api/v1/query) via unsanitized window-function name

CVSS 8.3 HighEPSS 0.0040 · 34th percentile

Published by the GitHub Advisory Database at 2 Oct 2026, 22:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
trigger.devnpm<4.5.64.5.6
Identifiers
GHSA-9q4r-4842-93vw · CVE-2026-114081
Weakness (CWE)
CWE-89 · CWE-639
Tags
Published
2 Oct 2026
Updated
21 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Trigger.dev versions before 4.5.6 are affected by a cross-tenant SQL injection in the TSQL query compiler, reachable through the POST /api/v1/query endpoint. Any authenticated customer, using a private API key or public JWT, can inject a backtick-quoted identifier into a window-function name that is inserted into the generated ClickHouse SQL without allowlisting or escaping. The injected subquery sits outside the tenant filter, so the attacker can read other organizations' analytics rows. The fix is to upgrade to trigger.dev 4.5.6 or later.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.3 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0040, the 34th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:33 UTC First seen by agentprime
  2. 31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.