Gitify
Monthly
Gitify desktop builds prior to 7.10.0 perform the GitHub web OAuth flow without generating or validating an OAuth `state` value, so an attacker who supplies their own authorization code via a crafted `gitify://oauth?code=...` deep link can bind a victim's Gitify client to the attacker's GitHub account. The attacker then controls the notifications the victim sees, but gains no access to the victim's data and no account takeover - impact is limited to low integrity. Exploitation is unauthenticated (PR:N) but requires a race against an already-pending login (AT:P) and victim interaction with the attacker's link (UI:P). No public exploit code or CISA KEV entry was identified at time of analysis, and the issue is assessed as genuinely low priority.
Gitify desktop builds prior to 7.10.0 perform the GitHub web OAuth flow without generating or validating an OAuth `state` value, so an attacker who supplies their own authorization code via a crafted `gitify://oauth?code=...` deep link can bind a victim's Gitify client to the attacker's GitHub account. The attacker then controls the notifications the victim sees, but gains no access to the victim's data and no account takeover - impact is limited to low integrity. Exploitation is unauthenticated (PR:N) but requires a race against an already-pending login (AT:P) and victim interaction with the attacker's link (UI:P). No public exploit code or CISA KEV entry was identified at time of analysis, and the issue is assessed as genuinely low priority.