CVE-2026-92773 json
Trigger.dev before 4.6.0 GitHub App Installation Takeover
published last mo. modified last mo. also EUVD-2026-81037 , GHSA-9rx3-j5hm-5f27
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository triggerdotdev/trigger.dev. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm trigger.dev >= 4.6.0
- triggerdotdev trigger.dev 4.6.0
Is CVE-2026-92773 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N |
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N |
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | trigger.dev | <=4.6.0 |
>= 4.6.0 |
Affected products
- triggerdotdev trigger.dev
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/triggerdotdev/trigger.dev/blob/v4.6.0/apps/webapp/app/services/gitHub.server.ts#L83-L86
patch
-
github.com
/triggerdotdev/trigger.dev/security/advisories/GHSA-9rx3-j5hm-5f27
third-party-advisory, vendor-advisory, advisory
-
github.com
/triggerdotdev/trigger.dev/blob/v4.5.16/apps/webapp/app/services/gitHub.server.ts
technical-description
-
github.com
/triggerdotdev/trigger.dev
product
-
vulncheck.com
/advisories/trigger-dev-before-4.6.0-github-app-installation-takeover
third-party-advisory
Sources
- CVE List CVE-2026-92773
- NVD CVE-2026-92773
- Maintainer advisory GHSA-9rx3-j5hm-5f27
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of triggerdotdev/trigger.dev published their own advisory on GitHub. Reviewed sources take precedence over it.