CVE-2026-110307

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

Published Nov 18, 2026 CVSS 4.0 · 7.4 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

An incorrect authorization flaw allows an authenticated user whose numeric user ID matches an enterprise’s numeric ID to manage that enterprise’s GitHub Apps and generate private keys without being a member of the enterprise. The ownership checks compare numeric IDs without validating account type, enabling an attacker to claim App ownership. Exploitation requires control or hijacking of a session for the colliding user account, after which the attacker can use the generated private key to authenticate as the App and read or modify repositories where the App is installed, limited by the App’s granted permissions. This flaw represents a significant privilege escalation that can grant unauthorized access to organizational code and secrets.

Affected Systems

GitHub Enterprise Server versions prior to 3.23 are affected. The vulnerability was fixed in releases 3.19.16, 3.20.12, 3.21.10, and 3.22.5, and will be present in any earlier supported release.

Risk and Exploitability

The CVSS score of 7.4 indicates high severity, and the flaw is not listed in the CISA KEV catalog. Exploitation requires an authenticated session for a colliding user ID, so the attack surface is limited to users whose numeric ID matches an enterprise ID; however, the availability of such collisions and the ability to generate a private key increases the risk to repositories installed for the app. The EPSS score of < 1% suggests a very low probability of exploitation, yet the impact of successful exploitation remains high.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade GitHub Enterprise Server to a fixed release – 3.19.16, 3.20.12, 3.21.10, 3.22.5 or any later 3.23+ version.
  • Validate that no user ID collides with an enterprise ID; disable or rename offending accounts or enterprises to remove collisions.
  • Rotate private keys for all GitHub Apps that were installed before the patch, especially if they were accessed by a user that could have performed the exploit.
  • Monitor for abnormal App activity and enforce least privilege for App permissions.

Generated by OpenCVE AI on November 19, 2026 at 00:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Github
Github enterprise Server
Vendors & Products Github
Github enterprise Server
Type Values Removed Values Added
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.
Title Incorrect authorization vulnerability in GitHub Enterprise Server allowed unauthorized control of enterprise-owned GitHub Apps via user and enterprise ID collision
Weaknesses CWE-1025
References
Metrics cvssV4_0

{'score': 7.4, 'vector': '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'}

Weaknesses
  • CWE-1025

    Comparison Using Wrong Factors

Sources

Status
PUBLISHED
Assigner
GitHub_P
Published
Updated
Nov 18, 2026, 5:38 PM
Reserved
Oct 13, 2026, 7:53 PM
Status
Received
Published
Nov 18, 2026, 2:17 AM
Modified
Nov 18, 2026, 6:17 PM