Skip to main content
VulnerabilityPublished

CVE-2026-111801: GitHub Enterprise Server · Insecure Direct Object Reference

Affects GitHub Enterprise ServerSource CVE Database V5

0
Compare

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, 01:35 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 GitHub 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

Upgrade GitHub Enterprise Server to version 3.21.10 or later, or 3.22.5 or later, where this vulnerability has been fixed. No other mitigation or workaround is indicated by the vendor advisory.

Description

CVE-2026-111801 is an authorization bypass vulnerability in GitHub Enterprise Server versions 3.21.0 through 3.21.9 and 3.22.0 through 3.22.4. Authenticated users could exploit this flaw to read review-thread data from private repositories they do not have access to by supplying user-controlled thread identifiers to the thread-preview endpoint. This exposure includes private file paths, source code excerpts, commit IDs, and line metadata without requiring victim interaction. The issue was fixed in versions 3.21.10 and 3.22.5.

References

Community reviews

Loading reviews…