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.