CVE-2026-111801

Authorization bypass through user-controlled key vulnerability in GitHub Enterprise Server allowed disclosure of private pull request review-thread data

Published Nov 18, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

An authorization bypass vulnerability in GitHub Enterprise Server exposes review-thread data from private repositories to authenticated users that normally could not access it. The flaw lies in the thread-preview endpoint, which accepts a review-thread identifier supplied by the user and resolves it without confirming that the thread belongs to the requested pull request. The result is the leakage of private file paths, source-code excerpts, commit identifiers, and line metadata. This weakness is a classic improper authorization problem.

Affected Systems

GitHub Enterprise Server versions in the 3.21 and 3.22 release lines prior to 3.21.10 and 3.22.5, respectively, are affected. The fix was released in those versions.

Risk and Exploitability

Based on the description, the likely attack vector is an authenticated user with read access to a repository and a pull request who supplies a target review-thread identifier to the thread-preview endpoint. The vulnerability requires no additional privileges beyond normal repository access and no victim interaction; an attacker merely queries the API. The CVSS score of 7.1 indicates high severity. The EPSS score of < 1% suggests a low yet nonzero probability of exploitation. The vulnerability is not listed in CISA KEV, and the exploitation potential remains limited to internal or collaborator users who already have access to the private repositories.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update GitHub Enterprise Server to version 3.21.10 or later in the 3.21 line, or 3.22.5 or later in the 3.22 line, to apply the vendor’s fix.
  • If an immediate update is not possible, restrict or disable the thread-preview endpoint for private repositories, ensuring that clients can only access review-thread data for pull requests they are explicitly authorized to view.
  • Review repository permissions and audit user access to confirm that only necessary personnel have the ability to read private pull-request data.

Generated by OpenCVE AI on November 19, 2026 at 00:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Github
Github enterprise Server
Vendors & Products Github
Github enterprise Server
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

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
GitHub_P
Published
Updated
Nov 18, 2026, 5:37 PM
Reserved
Oct 16, 2026, 7:27 PM
Status
Received
Published
Nov 18, 2026, 1:17 AM
Modified
Nov 18, 2026, 6:17 PM