CVE-2026-75101: Authorization bypass vulnerability in GitHub Enterprise Server allowed reading of private pull request diffs and patches via repository name collision
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.17.21 - Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.18.15 - Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.19.12 - Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.20.8 - Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.21.6
Event History
Frequently Asked Questions
Who could exploit this issue?
Any authenticated user of the affected GitHub Enterprise Server instance could exploit it. The attacker needed to know the target private repository's name and a valid pull request number.
What access could an attacker obtain?
An attacker could read the raw diff or patch for pull requests in private repositories without being authorized to access those repositories. The issue exposed pull request contents through raw diff and patch retrieval.
Are default deployments affected?
All GitHub Enterprise Server versions before 3.22 were affected; the provided information does not identify any configuration prerequisite or mitigation. The vulnerability was fixed in 3.17.21, 3.18.15, 3.19.12, 3.20.8, and 3.21.6.
How did the repository-name collision enable the bypass?
Tokens for raw pull request diffs and patches were scoped to a repository name and pull request number, rather than a globally unique repository identifier. An attacker could create a repository and pull request matching those values and use a token from their own repository to request the target pull request's contents.