Trigger.dev: 25 Vulnerabilities Disclosed in Single Batch, Ranging from Auth Bypass to SQLi
A coordinated disclosure on October 21, 2026, revealed 25 vulnerabilities in Trigger.dev, including critical flaws in authentication, authorization, SQL injection, and SSRF.

Key findings
- 25 Trigger.dev vulnerabilities disclosed on October 21, 2026, spanning multiple severity levels.
- High-severity flaws include authentication bypass, SQL injection, and authorization issues.
- Multiple CVEs exploit SSRF and CSRF vulnerabilities, posing risks to user sessions and internal systems.
- Information disclosure vulnerabilities can expose sensitive API keys and environment secrets.
- Patches are available in versions up to 4.7.6; immediate updates are recommended.
On October 21, 2026, a significant batch of 25 vulnerabilities was disclosed for Trigger.dev, impacting various versions prior to 4.7.6. These vulnerabilities, ranging in severity from Low to High, were all disclosed on the same day, indicating a coordinated disclosure event. The issues primarily revolve around authentication bypass, authorization flaws, SQL injection, cross-site request forgery (CSRF), path traversal, and server-side request forgery (SSRF), collectively posing a substantial risk to users of the platform.
Several vulnerabilities center on authentication and authorization bypass. CVE-2026-114090 (High) and CVE-2026-114087 (High) allow unauthenticated attackers to bypass authentication mechanisms, with CVE-2026-114087 enabling login as any email address by forging magic link tokens in self-hosted Docker Compose deployments. CVE-2026-114092 (Medium) and CVE-2026-114091 (Medium) permit attackers to replay runs into unintended environments by exploiting the lookup of runs via friendlyId alone. Furthermore, CVE-2026-114089 (High) allows for the minting of Personal Access Tokens without user consent via a CSRF vulnerability in the CLI authorization-code flow. CVE-2026-114088 (Medium) exposes a hardcoded default secret in the coordinator Socket.IO namespace, allowing unauthenticated attackers to retrieve decrypted environment variables. CVE-2026-114078 (High) and CVE-2026-114077 (High) enable authenticated users to delete or disable other organizations' schedules and bypass authorization in deployment background worker creation, respectively. CVE-2026-114069 (High) is particularly concerning as it exposes the environment's root API key for staging, production, and preview environments via the /api/v1/projects/:projectRef/envvars endpoint.
Other critical vulnerabilities include SQL injection flaws. CVE-2026-114084 (High) and CVE-2026-114081 (High) exploit the TSQL query compiler and the /realtime/v1/runs endpoint, respectively, allowing authenticated attackers to inject malicious SQL queries. Path traversal is addressed in CVE-2026-114083 (High), where authenticated tenants can escape their object key prefix through unsanitized filename segments in the api/v1/packets and api/v2/packets endpoints.
Server-side request forgery (SSRF) is another prominent theme. CVE-2026-114080 (Medium) and CVE-2026-114076 (Medium) allow authenticated users to make the server send requests to internal hosts or cloud metadata addresses by setting unvalidated alert-channel webhook URLs. CVE-2026-114074 (Medium) bypasses SSRF protections by targeting the 198.18.0.0/15 benchmarking range.
Cross-site request forgery (CSRF) vulnerabilities are present in CVE-2026-114093 (Medium), which allows remote attackers to log out users by tricking them into clicking a malicious link, and CVE-2026-114072 (Medium), affecting the organization-level Slack OAuth flow.
Information disclosure vulnerabilities include CVE-2026-114073 (Medium), which exposes resolved environment secret values in debug deployment logs, and CVE-2026-114070 (Low), which stores a delegated user-actor token in browser-readable session input records.
The affected versions span a wide range, with patches available in Trigger.dev versions 4.5.0 through 4.6.2, and 4.7.6. Users are strongly advised to update to the latest available versions to mitigate these risks. The sheer number and variety of vulnerabilities disclosed simultaneously highlight the importance of prompt patching and security reviews for Trigger.dev users.
This extensive batch of vulnerabilities underscores the need for continuous security vigilance. Users of Trigger.dev should prioritize updating their installations to the patched versions as soon as possible. The diverse nature of these flaws, from authentication bypass to SQL injection and SSRF, indicates potential systemic weaknesses that may require thorough investigation by the vendor. Staying informed about security advisories and applying patches promptly is crucial for maintaining the integrity and security of their Trigger.dev deployments.
Key findings include:
- A large batch of 25 vulnerabilities disclosed on October 21, 2026, affecting Trigger.dev.
- Multiple high-severity vulnerabilities related to authentication and authorization bypass.
- Significant risks from SQL injection, path traversal, and SSRF vulnerabilities.
- Cross-site request forgery (CSRF) flaws impacting user sessions and OAuth flows.
- Information disclosure vulnerabilities exposing sensitive secrets and tokens.
- Patches are available in versions up to 4.7.6, with users urged to update immediately.