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
·
Updated

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.

Affected Software

1 affected component
GitHub GitHub Enterprise Server>=3.19.0<3.19.16, >=3.20.0<3.20.12, >=3.21.0<3.21.10, >=3.22.0<3.22.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.19.16
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.20.12
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.21.10
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.22.5

Event History

Nov 18, 2026
CVE Published
via MITRE·01:12 AM
Data Sourced
via MITRE·01:12 AM
DescriptionWeakness
Data Sourced
via NVD·02:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which GitHub Enterprise Server versions contain the fix?

The issue was fixed in GitHub Enterprise Server 3.19.16, 3.20.12, 3.21.10, and 3.22.5. Supported releases before 3.23 were affected.

2

What conditions are required for exploitation?

An attacker needs control of a session for a user account whose numeric ID collides with an enterprise numeric ID, and the enterprise must own a GitHub App. The attacker does not need enterprise membership.

3

Are standard fresh installations readily exploitable?

On standard fresh installations, the documented colliding account was the built-in ghost account, which cannot log in. The reported GitHub Enterprise Server reproduction used site administrator impersonation.

4

What is the impact if an attacker generates an affected GitHub App private key?

The private key can authenticate the attacker as that GitHub App. They can then access repositories where the App is installed, limited to the permissions granted to the App.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203