Gitify before 7.10.0 contains a login cross-site request forgery vulnerability that allows remote attackers to bind a victim's client to their account because performGitHubWebOAuth() omits OAuth state validation. Attackers can get a gitify://oauth?code= link with their own authorization code opened during a victim's pending login, causing Gitify to display attacker-controlled notifications as the victim's own.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 2
- StatusReceived → DeferredNVD modified 2026-10-19 21:14
- First seenCVSS 2.3NVD modified 2026-10-19 17:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/gitify-app/gitify/blob/v7.9.0/src/renderer/utils/forges/github/flows.ts#L35-L76
- https://github.com/gitify-app/gitify/commit/10235b243e167a7c76eafd6a3d0ebc8c575eebc7
- https://github.com/gitify-app/gitify/issues/3425
- https://github.com/gitify-app/gitify/releases/tag/v7.10.0
- https://www.vulncheck.com/advisories/gitify-before-7.10.0-login-csrf-via-missing-oauth-state-validation