CVE-2026-4296: CWE-185 Incorrect Regular Expression in GitHub Enterprise Server
CVE-2026-4296 is a high-severity vulnerability in GitHub Enterprise Server prior to version 3. 21 involving an incorrect regular expression that allows bypassing OAuth redirect URI validation. An attacker who knows a legitimate OAuth application's registered callback URL can craft a malicious authorization link that redirects the OAuth authorization code to an attacker-controlled domain. This could enable unauthorized access to the victim's account with the OAuth application's granted scopes. The issue affects multiple versions before 3. 21 and was fixed in several patch releases starting from 3. 14. 26 up to 3. 20. 1.
AI Analysis
Technical Summary
This vulnerability arises from an incorrect regular expression used in GitHub Enterprise Server's OAuth redirect URI validation, classified as CWE-185. It allows an attacker with knowledge of a first-party OAuth application's registered callback URL to create 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 permissions granted to the OAuth application. The vulnerability affects all GitHub Enterprise Server versions prior to 3.21 and was addressed in patch releases 3.14.26, 3.15.21, 3.16.17, 3.17.14, 3.18.8, 3.19.5, and 3.20.1. The vulnerability was responsibly disclosed via the GitHub Bug Bounty program.
Potential Impact
Successful exploitation can lead to unauthorized access to user accounts on GitHub Enterprise Server with the OAuth application's granted scopes. This could result in account compromise and unauthorized actions performed under the victim's identity. The vulnerability requires user interaction (clicking a crafted link) and some level of attacker knowledge (the legitimate OAuth callback URL). No known active exploits have been reported.
Mitigation Recommendations
A fix is available and has been released in GitHub Enterprise Server versions 3.14.26, 3.15.21, 3.16.17, 3.17.14, 3.18.8, 3.19.5, and 3.20.1. Users and administrators should upgrade affected GitHub Enterprise Server instances to one of these patched versions or later to remediate this vulnerability. Since this is not a cloud service, patching the server is required. Patch status is confirmed by the vendor advisory embedded in the description.
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 prior to version 3. 21 involving an incorrect regular expression that allows bypassing OAuth redirect URI validation. An attacker who knows a legitimate OAuth application's registered callback URL can craft a malicious authorization link that redirects the OAuth authorization code to an attacker-controlled domain. This could enable unauthorized access to the victim's account with the OAuth application's granted scopes. The issue affects multiple versions before 3. 21 and was fixed in several patch releases starting from 3. 14. 26 up to 3. 20. 1.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability arises from an incorrect regular expression used in GitHub Enterprise Server's OAuth redirect URI validation, classified as CWE-185. It allows an attacker with knowledge of a first-party OAuth application's registered callback URL to create 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 permissions granted to the OAuth application. The vulnerability affects all GitHub Enterprise Server versions prior to 3.21 and was addressed in patch releases 3.14.26, 3.15.21, 3.16.17, 3.17.14, 3.18.8, 3.19.5, and 3.20.1. The vulnerability was responsibly disclosed via the GitHub Bug Bounty program.
Potential Impact
Successful exploitation can lead to unauthorized access to user accounts on GitHub Enterprise Server with the OAuth application's granted scopes. This could result in account compromise and unauthorized actions performed under the victim's identity. The vulnerability requires user interaction (clicking a crafted link) and some level of attacker knowledge (the legitimate OAuth callback URL). No known active exploits have been reported.
Mitigation Recommendations
A fix is available and has been released in GitHub Enterprise Server versions 3.14.26, 3.15.21, 3.16.17, 3.17.14, 3.18.8, 3.19.5, and 3.20.1. Users and administrators should upgrade affected GitHub Enterprise Server instances to one of these patched versions or later to remediate this vulnerability. Since this is not a cloud service, patching the server is required. Patch status is confirmed by the vendor advisory embedded in the description.
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/21/2026, 10:46:20 PM
Last updated: 4/22/2026, 12:40:39 AM
Views: 6
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.