---
id: "CVE-2026-112050"
kind: "vulnerability"
aliases: ["CVE-2026-112050"]
title: "Gitify: missing OAuth state check lets attackers bind victim's GitHub login"
severity: "low"
cvss: 3.1
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["desktop", "github", "gitify", "oauth", "package"]
not_affected_if: ["default-config"]
published_at: "2026-10-18T13:16:37+00:00"
first_seen_at: "2026-10-23T21:57:15+00:00"
updated_at: "2026-10-25T04:47:48+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112050", "first_seen_at": "2026-10-23T21:57:15+00:00"}]
---

# Gitify: missing OAuth state check lets attackers bind victim's GitHub login

Gitify, a desktop GitHub notifications client, skips OAuth state validation during login, so a crafted gitify:// link can swap in the attacker's authorization code. The victim's Gitify then shows the attacker's GitHub notifications as their own.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Gitify version in the app's About dialog or package metadata; versions below `7.10.0` are affected.
- unknown

## Fix

- Upgrade Gitify to `7.10.0` or later.
- Sign out and sign back in after upgrading if the client was logged in during a pending login window.

## Timeline

- 2026-10-23T21:57:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-112050

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_