CVE-2026-92773: Authorization Bypass Through User-Controlled Key in triggerdotdev trigger.dev
Trigger.dev before 4.6.0 fails to verify that an authenticated user controls a GitHub App installation before binding it to their organization. Attackers can claim another user's GitHub App installation by replaying state cookies and supplying sequential installation identifiers, gaining unauthorized access to the victim's repositories.
AI Analysis
Technical Summary
CVE-2026-92773 is an authorization bypass vulnerability in trigger.dev prior to version 4.6.0. The issue arises because the application fails to verify ownership of a GitHub App installation when binding it to an organization. Attackers can exploit this by replaying state cookies and supplying sequential installation IDs to impersonate other users' GitHub App installations, thereby accessing repositories without proper authorization.
Potential Impact
Successful exploitation allows an attacker with low privileges to gain unauthorized access to repositories belonging to other users by hijacking their GitHub App installations. This could lead to unauthorized repository access, potentially exposing sensitive code or data. The vulnerability has a CVSS 4.0 base score of 7.1 (high severity), indicating significant impact but requiring some attack complexity and partial user interaction.
Mitigation Recommendations
Upgrade trigger.dev to version 4.6.0 or later, where this authorization verification issue has been fixed. Since this is a self-hosted product, users must apply the official patch or update to the fixed version to remediate the vulnerability. Patch status is confirmed by the affectedVersions field indicating versions prior to 4.6.0 are vulnerable.
CVE-2026-92773: Authorization Bypass Through User-Controlled Key in triggerdotdev trigger.dev
Description
Trigger.dev before 4.6.0 fails to verify that an authenticated user controls a GitHub App installation before binding it to their organization. Attackers can claim another user's GitHub App installation by replaying state cookies and supplying sequential installation identifiers, gaining unauthorized access to the victim's repositories.
CVSS v4.0
Score 7.1high
Affected software
triggerdotdev
trigger.dev
pkg:github/triggerdotdev/trigger.devRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-92773 is an authorization bypass vulnerability in trigger.dev prior to version 4.6.0. The issue arises because the application fails to verify ownership of a GitHub App installation when binding it to an organization. Attackers can exploit this by replaying state cookies and supplying sequential installation IDs to impersonate other users' GitHub App installations, thereby accessing repositories without proper authorization.
Potential Impact
Successful exploitation allows an attacker with low privileges to gain unauthorized access to repositories belonging to other users by hijacking their GitHub App installations. This could lead to unauthorized repository access, potentially exposing sensitive code or data. The vulnerability has a CVSS 4.0 base score of 7.1 (high severity), indicating significant impact but requiring some attack complexity and partial user interaction.
Mitigation Recommendations
Upgrade trigger.dev to version 4.6.0 or later, where this authorization verification issue has been fixed. Since this is a self-hosted product, users must apply the official patch or update to the fixed version to remediate the vulnerability. Patch status is confirmed by the affectedVersions field indicating versions prior to 4.6.0 are vulnerable.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-16T19:15:39.366Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aab005f55bf5e2cf5231df8
Added to database: 09/16/2026, 20:47:27 UTC
Last enriched: 09/16/2026, 22:01:30 UTC
Last updated: 09/16/2026, 23:41:36 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.