CVE-2026-4296: CWE-185 Incorrect Regular Expression in GitHub Enterprise Server
CVE-2026-4296 is a high-severity vulnerability in GitHub Enterprise Server involving an incorrect regular expression that allowed bypassing OAuth redirect URI validation. An attacker who knows a legitimate OAuth application's callback URL could craft a malicious authorization link to redirect OAuth authorization codes to attacker-controlled domains. This could enable unauthorized access to victim accounts with the OAuth application's granted scopes. The issue affects all GitHub Enterprise Server versions prior to 3. 21 and was fixed in versions 3. 20. 1 and later. No known exploits in the wild have been reported.
AI Analysis
Technical Summary
This vulnerability arises from an incorrect regular expression in GitHub Enterprise Server's OAuth redirect URI validation logic. It allows an attacker with knowledge of a first-party OAuth application's registered callback URL to bypass validation by crafting a malicious authorization link. When a victim clicks this link, the OAuth authorization code is redirected to an attacker-controlled domain, potentially granting the attacker unauthorized access to the victim's account with the OAuth application's scopes. The vulnerability affects versions prior to 3.21 and was addressed in multiple patch releases starting with 3.20.1.
Potential Impact
Successful exploitation can lead to unauthorized access to user accounts on GitHub Enterprise Server with the permissions granted to the OAuth application. This could result in account compromise and unauthorized actions performed under the victim's identity. The vulnerability is rated high severity with a CVSS 4.0 score of 7.5, reflecting network attack vector, low attack complexity, and partial user interaction required.
Mitigation Recommendations
A fix is available in GitHub Enterprise Server versions 3.20.1, 3.19.5, 3.18.8, 3.17.14, 3.16.17, 3.15.21, and 3.14.26. Users should upgrade to one of these patched versions or later to remediate this vulnerability. Since this is not a cloud service, administrators must apply the update manually. Patch status is confirmed by the vendor advisory and the GitHub Bug Bounty program disclosure.
CVE-2026-4296: CWE-185 Incorrect Regular Expression in GitHub Enterprise Server
Description
CVE-2026-4296 is a high-severity vulnerability in GitHub Enterprise Server involving an incorrect regular expression that allowed bypassing OAuth redirect URI validation. An attacker who knows a legitimate OAuth application's callback URL could craft a malicious authorization link to redirect OAuth authorization codes to attacker-controlled domains. This could enable unauthorized access to victim accounts with the OAuth application's granted scopes. The issue affects all GitHub Enterprise Server versions prior to 3. 21 and was fixed in versions 3. 20. 1 and later. No known exploits in the wild have been reported.
CVSS v4.0
Score 7.5high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability arises from an incorrect regular expression in GitHub Enterprise Server's OAuth redirect URI validation logic. It allows an attacker with knowledge of a first-party OAuth application's registered callback URL to bypass validation by crafting a malicious authorization link. When a victim clicks this link, the OAuth authorization code is redirected to an attacker-controlled domain, potentially granting the attacker unauthorized access to the victim's account with the OAuth application's scopes. The vulnerability affects versions prior to 3.21 and was addressed in multiple patch releases starting with 3.20.1.
Potential Impact
Successful exploitation can lead to unauthorized access to user accounts on GitHub Enterprise Server with the permissions granted to the OAuth application. This could result in account compromise and unauthorized actions performed under the victim's identity. The vulnerability is rated high severity with a CVSS 4.0 score of 7.5, reflecting network attack vector, low attack complexity, and partial user interaction required.
Mitigation Recommendations
A fix is available in GitHub Enterprise Server versions 3.20.1, 3.19.5, 3.18.8, 3.17.14, 3.16.17, 3.15.21, and 3.14.26. Users should upgrade to one of these patched versions or later to remediate this vulnerability. Since this is not a cloud service, administrators must apply the update manually. Patch status is confirmed by the vendor advisory and the GitHub Bug Bounty program disclosure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_P
- Date Reserved
- 2026-03-16T17:48:03.040Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e7faaa19fe3cd2cd00149b
Added to database: 4/21/2026, 10:31:06 PM
Last enriched: 4/29/2026, 11:44:35 AM
Last updated: 6/4/2026, 10:59:26 AM
Views: 75
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.