Skip to main content
VulnerabilityPublished

CVE-2026-110307: GitHub Enterprise Server · Comparison Using Wrong Factors

Affects GitHub Enterprise ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High · fixed in 3.22.5 : patch GitHub Enterprise Server soon.

Data as of 18 Nov 2026, 01:35 UTC

CVSS 4.0 base score
7.4High
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.4
Patch
Available – fixed in 3.22.5, 3.21.10, 3.20.12 +1
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/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, 3.21.10, 3.20.12 or 3.19.16.

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
GitHubEnterprise ServerAffected
  • >=3.20.0 <3.20.12
Fixed in
  • 3.20.12
GitHubEnterprise ServerAffected
  • >=3.19.0 <3.19.16
Fixed in
  • 3.19.16

AI-suggested

This vulnerability has been fixed in GitHub Enterprise Server versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. Users should upgrade to one of these fixed versions or later to remediate the issue.

Description

CVE-2026-110307 is an authorization vulnerability in GitHub Enterprise Server that allowed authenticated users with numeric user IDs matching an enterprise's numeric ID to manage that enterprise's GitHub Apps and generate private keys without membership. The flaw was due to ownership checks comparing numeric IDs without verifying account types. Exploitation required control of a session for the colliding user and an enterprise-owned GitHub App. The vulnerability affected versions prior to 3.19.16, 3.20.12, 3.21.10, and 3.22.5 and has been fixed in those releases.

References

Community reviews

Loading reviews…