Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 18 Nov 2026 01:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Authorization bypass through user-controlled key vulnerability in GitHub Enterprise Server allowed disclosure of private pull request review-thread data | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_P
Published:
Updated: 2026-11-18T01:04:41.938Z
Reserved: 2026-10-16T19:27:54.325Z
Link: CVE-2026-111801
No data.
Status : Received
Published: 2026-11-18T01:17:49.223
Modified: 2026-11-18T01:17:49.223
Link: CVE-2026-111801
No data.
OpenCVE Enrichment
No data.
-
CWE-639
Authorization Bypass Through User-Controlled Key