CVE-2026-96890: GitHub Enterprise Server · Server-Side Request Forgery (SSRF)
Affects GitHub Enterprise ServerSource CVE Database V5
Not known to be exploited · CVSS 8.7 High · fixed in 3.22.2 : patch GitHub Enterprise Server soon.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.22.2, 3.21.7, 3.20.9
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 20 Nov 2026.
What to do
Upgrade GitHub Enterprise Server to 3.22.2, 3.21.7 or 3.20.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GitHubEnterprise Server | Affected
| Fixed in
|
| GitHubEnterprise Server | Affected
| Fixed in
|
| GitHubEnterprise Server | Affected
| Fixed in
|
AI-suggested
A fix is available and has been released in GitHub Enterprise Server versions 3.20.9, 3.21.7, and 3.22.2. Administrators should upgrade affected instances to these or later versions to remediate the vulnerability. Since this is a server product, the vendor does not manage remediation for cloud services. No additional mitigation steps are indicated beyond applying the official patches.
Description
A Server-Side Request Forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed a repository contributor to cause the appliance to issue requests to attacker-controlled internal hosts, which could be chained to achieve remote code execution on the appliance. The secret scanning validator for GCP service account credentials trusted the token endpoint embedded in a committed credential and issued a request to it without restricting the destination. Exploitation required an authenticated user with permission to push to a repository on an instance with GitHub Advanced Security and secret scanning validity checks enabled, a non-default configuration. This vulnerability affected GitHub Enterprise Server 3.20, 3.21, and 3.22 and was fixed in versions 3.20.9, 3.21.7, and 3.22.2. This vulnerability was reported through the GitHub Bug Bounty program.