CVE-2026-111801: Authorization bypass through user-controlled key vulnerability in GitHub Enterprise Server allowed disclosure of private pull request review-thread data
An authorization bypass through user-controlled key vulnerability was identified in GitHub Enterprise Server that allowed authenticated users to read review-thread data from private repositories they could not access. An attacker required an authenticated account, a readable repository and pull request to use as the request context, and target review-thread identifiers. The thread-preview endpoint resolved supplied identifiers without restricting them to the authorized pull request, exposing private file paths and, when positioning and diff data were available, source-code excerpts, commit identifiers, and line metadata without victim interaction. This vulnerability affected supported GitHub Enterprise Server releases in the 3.21, 3.22 series and was fixed in versions 3.21.10, 3.22.5. 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.21.10 - Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.22.5
Event History
Frequently Asked Questions
Which GitHub Enterprise Server versions contain the fix?
The issue was fixed in GitHub Enterprise Server 3.21.10 and 3.22.5. Affected supported release series are 3.21 and 3.22.
Can an unauthenticated internet user exploit this issue?
No. Exploitation requires an authenticated account, as well as access to a readable repository and pull request that can be used as request context.
What information could be disclosed?
An attacker could read private review-thread data from repositories they were not authorized to access. Exposed data could include private file paths and, where available, source-code excerpts, commit identifiers, and line metadata.