CVE-2026-4296: Incorrect Regular Expression vulnerability in GitHub Enterprise Server allowed unauthorized access to user accounts via OAuth callback URL validation bypass
An incorrect regular expression vulnerability was identified in GitHub Enterprise Server that allowed an attacker to bypass OAuth redirect URI validation. An attacker with knowledge of a first-party OAuth application's registered callback URL could craft a malicious authorization link that, when clicked by a victim, would redirect the OAuth authorization code to an attacker-controlled domain. This could allow the attacker to gain unauthorized access to the victim's account with the scopes granted to the OAuth application. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.20.1, 3.19.5, 3.18.8, 3.17.14, 3.16.17, 3.15.21, 3.14.26. This vulnerability was reported via the GitHub Bug Bounty program.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-4296?
CVE-2026-4296 has a high severity rating due to its potential to allow unauthorized access to user accounts.
How do I fix CVE-2026-4296?
To fix CVE-2026-4296, upgrade GitHub Enterprise Server to version 3.22 or later, which contains the necessary security patches.
What versions of GitHub Enterprise Server are affected by CVE-2026-4296?
CVE-2026-4296 affects all versions of GitHub Enterprise Server prior to 3.22.
What type of vulnerability is CVE-2026-4296?
CVE-2026-4296 is classified as an Incorrect Regular Expression vulnerability.
How can attackers exploit CVE-2026-4296?
Attackers can exploit CVE-2026-4296 by bypassing OAuth redirect URI validation, gaining unauthorized access to user accounts.