CVE-2026-9132: Missing authorization vulnerability in GitHub Enterprise Server allowed disclosure of private repository contents via the Copilot pull request diff summary endpoint
A missing authorization vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user to read source code from private repositories they did not have access to. The Copilot pull request description diff summary endpoint accepted a cross-repository comparison range and rendered the resulting diff without verifying that the requesting user was authorized to view the target repository. Exploitation required an authenticated account on the instance with read access to at least one repository to use as the comparison base. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.17.17, 3.18.11, 3.19.8, and 3.20.4. 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.17 - Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.18.11 - Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.19.8 - Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.20.4
Event History
Frequently Asked Questions
What is the severity of CVE-2026-9132?
CVE-2026-9132 has a medium severity rating with a CVSS score of 4.0.
How does CVE-2026-9132 affect GitHub Enterprise Server?
CVE-2026-9132 allows an authenticated user to access private repository contents they shouldn't have access to via the Copilot pull request diff summary endpoint.
What is the risk factor associated with CVE-2026-9132?
CVE-2026-9132 has a risk factor of 27.
How can organizations protect against CVE-2026-9132?
Organizations should ensure proper authorization checks are implemented for accessing private repository contents.
When was CVE-2026-9132 published?
CVE-2026-9132 was published on June 30, 2026.