Skip to main content
VulnerabilityPublished Updated

CVE-2026-75101: GitHub Enterprise Server · Authorization Bypass Vulnerability Was Identified

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-75101· Medium 6.0

Not known to be exploited · CVSS 6.0 Medium · fixed in 3.21.6 : update Enterprise Server when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.21.6, 3.20.8, 3.19.12 +2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 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 to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
GitHubEnterprise ServerAffected
  • >=3.21.0 <3.21.6
Fixed in
  • 3.21.6
GitHubEnterprise ServerAffected
  • >=3.20.0 <3.20.8
Fixed in
  • 3.20.8
GitHubEnterprise ServerAffected
  • >=3.19.0 <3.19.12
Fixed in
  • 3.19.12
GitHubEnterprise ServerAffected
  • >=3.18.0 <3.18.15
Fixed in
  • 3.18.15
GitHubEnterprise ServerAffected
  • >=3.17.0 <3.17.21
Fixed in
  • 3.17.21

AI-suggested

This vulnerability has been fixed in GitHub Enterprise Server versions 3.17.21, 3.18.15, 3.19.12, 3.20.8, and 3.21.6. Users should upgrade to one of these fixed versions or later to remediate the issue. No other mitigation is required once patched.

Description

An authorization bypass vulnerability in GitHub Enterprise Server allowed any authenticated user to read raw diffs or patches of pull requests in private repositories without proper authorization. The issue stemmed from access tokens being scoped to repository name and pull request number rather than a globally unique repository identifier. This enabled an attacker who created a repository and pull request with matching names and numbers to access private pull request contents. The vulnerability affected all versions prior to 3.22 and was fixed in versions 3.17.21, 3.18.15, 3.19.12, 3.20.8, and 3.21.6. Exploitation required knowledge of the target repository name and a valid pull request number. The CVSS score is 6.5 (medium severity).

References

Community reviews

Loading reviews…