CVE-2026-112050 Gitify before 7.10.0 Login CSRF via Missing OAuth State Validation
Attackers can bind a victim's Gitify client to their account via missing OAuth state validation, displaying attacker-controlled notifications as the victim's.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-112050?
CVE-2026-112050 is a low-severity vulnerability in gitify-app gitify, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-352
Which versions are affected by CVE-2026-112050?
How do I fix CVE-2026-112050?
No fix has been published for CVE-2026-112050 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-112050 being exploited?
There is no known exploitation of CVE-2026-112050 in the wild and no public exploit code.
Sources
Also known as GHSA-gh5g-g72j-mxwx.