Skip to main content
VulnerabilityPublished

CVE-2026-4296: GitHub Enterprise Server · Incorrect Regular Expression

Affects GitHub Enterprise ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High · fixed in 3.20.1 : patch GitHub Enterprise Server soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.20.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubEnterprise ServerAffected
  • >=3.14.0 <3.14.26
  • >=3.15.0 <3.15.21
  • >=3.16.0 <3.16.17
  • >=3.17.0 <3.17.14
  • >=3.18.0 <3.18.8
  • >=3.19.0 <3.19.5
  • >=3.20.0 <3.20.1
Fixed in–

AI-suggested

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.

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.

References

Community reviews

Loading reviews…