Skip to main content
CVE-2026-111801VulnerabilityPublished

An authorization bypass through user-controlled key vulnerability was identified in GitHub Enterprise Server that

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-111801· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 3.22.5 or 3.21.10 soon.

Data as of 18 Nov 2026, 05:21 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_P)CVSS 4.07.1
Patch
Available – fixed in 3.22.5, 3.21.10
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Enterprise Server to 3.22.5 or 3.21.10.

Affected software

ProductAffectedFixed in
GitHubEnterprise ServerAffected
  • >=3.22.0 <3.22.5
Fixed in
  • 3.22.5
GitHubEnterprise ServerAffected
  • >=3.21.0 <3.21.10
Fixed in
  • 3.21.10

AI-suggested

This vulnerability has been fixed in GitHub Enterprise Server versions 3.21.10 and 3.22.5. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in GitHub Enterprise Server allowed authenticated users to bypass authorization controls and read review-thread data from private repositories they could not normally access. The flaw involved the thread-preview endpoint resolving user-supplied review-thread identifiers without restricting them to the authorized pull request context. This exposed private file paths, source-code excerpts, commit identifiers, and line metadata. The issue affected versions in the 3.21 and 3.22 series and was fixed in 3.21.10 and 3.22.5.

References

Community reviews

Loading reviews…