CVE-2026-111801

7.1High

Published 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.1CVSS

High

0CVSS v4.010

Attack vector
Network
Complexity
Low
Privileges
Low
User action
None
Impact
High impact on confidentiality
Weakness
CWE-639

What an attacker gets

Authenticated attackers can read private review-thread data, including source code excerpts and file paths, from repositories they do not have access to. The attacker needs an existing account and knowledge of target review-thread identifiers.

Root cause

The thread-preview endpoint fails to validate that the requested review-thread identifier belongs to the pull request provided in the request context.

Affected versions

GitHub Enterprise Server 3.21.0 through 3.21.9 and 3.22.0 through 3.22.4.

CVSS v4.0 · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Fix & remediation

Upgrade to GitHub Enterprise Server 3.21.10 or 3.22.5. There is no known configuration-based mitigation for this endpoint bypass.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-111801