CVE Watchtower

CVE-2026-111801GitHub Enterprise Server Authorization Bypass Through User-Controlled Key

NVD

Vulnerability Summary

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 Level
HIGH(7.1)
Published Date
Nov 18, 2026
Last Modified
Nov 18, 2026
Exploitation Status
No confirmed exploitation yet
Root Weakness (CWE)
The system does not prevent one user from accessing another user data or record by modifying the key value identifying the data.
CVSS v4.0 Base Metrics — Score 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
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsNone
Privileges RequiredLow
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)None
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None

Affected & Patched Versions

Affected Versions
  • GitHub Enterprise Server >= 3.21.0 and < 3.21.*
  • GitHub Enterprise Server >= 3.22.0 and < 3.22.*
Patched Versions
  • GitHub Enterprise Server 3.21.*
  • GitHub Enterprise Server 3.22.*

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run GitHub Enterprise Server and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Nov 18, 2026Published
  • Nov 18, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new GitHub Enterprise Server CVEsYou are reading CVE-2026-111801. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More GitHub Enterprise Server CVEs

Data last checked: Nov 18, 2026 06:22 UTC