Skip to content
Threat Brief

← All advisories

CVE-2026-110307

High 7.4No known exploitationFix available

Incorrect authorization vulnerability in GitHub Enterprise Server allowed unauthorized control of enterprise-owned GitHub Apps via user and enterprise ID collision

Record last updated

CVSS score

7.4

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 22% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user whose numeric user ID matched an enterprise's numeric ID to manage that enterprise's GitHub Apps and generate private keys without enterprise membership. GitHub App ownership checks compared numeric IDs without checking the owner's account type. Exploitation required control of a session for the colliding user account and an enterprise-owned GitHub App. A generated private key could be used to authenticate as the App and access repositories where it was installed, within its granted permissions. On standard fresh installations, the documented collision involved the non-loginable built-in ghost account; the reported GHES reproduction used site administrator impersonation. This vulnerability affected supported GitHub Enterprise Server releases prior to 3.23 and was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. This vulnerability was reported via the GitHub Bug Bounty program.

Weakness: CWE-1025

Patching and mitigation

Patch status
Fix available (source: CVE record (GitHub_P))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
docs.github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
GitHubEnterprise Serverfrom 3.19.0 before 3.19.*Not documentedCVE Program
GitHubEnterprise Serverfrom 3.20.0 before 3.20.*Not documentedCVE Program
GitHubEnterprise Serverfrom 3.21.0 before 3.21.*Not documentedCVE Program
GitHubEnterprise Serverfrom 3.22.0 before 3.22.*Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by GitHub_P

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (GitHub_P)

    Source: CVE record (GitHub_P) (opens in a new tab)

Vendor guidance and references