cve.bz

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

7.1 highFix available

High (7.1) in github enterprise server.

On this page
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.

Severity

CVSS 4.0

7.1 high
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
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Assigned by
GitHub_P (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • GitHub Enterprise Server: fixed in 3.21.10
  • GitHub Enterprise Server: fixed in 3.22.5

Ask an AI about this CVE

Show the promptExplain CVE-2026-111801 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111801?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111801?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111801 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • github:enterprise server

Versions

From the CNA's record in the CVE List.

ProductAffected
GitHub Enterprise Serverfrom 3.21.0 before 3.21.*
GitHub Enterprise Serverfrom 3.22.0 before 3.22.*

Fixed in

ProductFixed in
GitHub Enterprise Server3.21.10
GitHub Enterprise Server3.22.5

References

Check your stackJSON