CVE-2026-75101: GitHub Enterprise Server · Insecure Direct Object Reference
Affects GitHub Enterprise ServerSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium · fixed in 3.21.6 : update GitHub Enterprise Server when convenient.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.21.6, 3.20.8, 3.19.12 +2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 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 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GitHubEnterprise Server | Affected
| Fixed in
|
| GitHubEnterprise Server | Affected
| Fixed in
|
| GitHubEnterprise Server | Affected
| Fixed in
|
| GitHubEnterprise Server | Affected
| Fixed in
|
| GitHubEnterprise Server | Affected
| Fixed in
|
AI-suggested
This vulnerability has been fixed in GitHub Enterprise Server versions 3.17.21, 3.18.15, 3.19.12, 3.20.8, and 3.21.6. Users should upgrade affected instances to one of these fixed versions or later to remediate the issue. No additional mitigation steps are indicated in the vendor advisory.
Description
An authorization bypass vulnerability was identified in GitHub Enterprise Server that allowed any authenticated user of the instance to read the raw diff or patch of pull requests in private repositories without authorization. Access tokens for raw pull request diffs and patches were scoped to the repository name and pull request number rather than to a globally unique repository identifier, so an attacker who created a repository and pull request matching a target's repository name and pull request number could use a token for their own repository to retrieve the private pull request's contents. Exploitation required the attacker to know the target repository's name and a valid pull request number. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.21, 3.18.15, 3.19.12, 3.20.8, and 3.21.6. This vulnerability was reported via the GitHub Bug Bounty program.
References
- docs.github.com/en/enterprise-server@3.17/admin/release-notes (opens in a new tab)
- docs.github.com/en/enterprise-server@3.18/admin/release-notes (opens in a new tab)
- docs.github.com/en/enterprise-server@3.19/admin/release-notes (opens in a new tab)
- docs.github.com/en/enterprise-server@3.20/admin/release-notes (opens in a new tab)
- docs.github.com/en/enterprise-server@3.21/admin/release-notes (opens in a new tab)