CVE-2026-9106: UI misrepresentation vulnerability in GitHub Enterprise Server allowed unauthorized organization runner management via undisclosed OAuth scope on consent screen

Published Jun 30, 2026
·
Updated

A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed an OAuth application to gain unintended access to an organization's runner management. An attacker could exploit this by creating an OAuth application requesting the managerunners:org scope and directing a victim user to authorize it, as the scope was not displayed on the authorization consent screen. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.21.2, 3.20.4, 3.19.8, 3.18.11, 3.17.17, 3.16.20. This vulnerability was reported via the GitHub Bug Bounty program.

Other sources

A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed an OAuth application to gain unintended access to an organization's runner management. An attacker could exploit this by creating an OAuth application requesting the managerunners:org scope and directing a victim user to authorize it, as the scope was not displayed on the authorization consent screen. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.21.2, 3.20.4, 3.19.8, 3.18.11, 3.17.17. This vulnerability was reported via the GitHub Bug Bounty program.

NVD

Affected Software

7 affected components
GitHub GitHub Enterprise Server<3.22
GitHub Enterprise Server<3.16.20
GitHub Enterprise Server>=3.17.0<3.17.17
GitHub Enterprise Server>=3.18.0<3.18.11
GitHub Enterprise Server>=3.19.0<3.19.8
GitHub Enterprise Server>=3.20.0<3.20.4
GitHub Enterprise Server>=3.21.0<3.21.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.17.17Patch 3.17.17
  2. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.18.11Patch 3.18.11
  3. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.19.8Patch 3.19.8
  4. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.20.4Patch 3.20.4
  5. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.21.2Patch 3.21.2

Event History

Jun 30, 2026
CVE Published
via MITRE·08:21 PM
Data Sourced
via MITRE·08:21 PM
DescriptionWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Jul 3, 58550
Event
via FIRST·07:51 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-9106?

CVE-2026-9106 has a medium severity rating of 4.8 according to CVSS.

2

How do I fix CVE-2026-9106?

To mitigate CVE-2026-9106, users should update their GitHub Enterprise Server to the latest version where the vulnerability is addressed.

3

What does CVE-2026-9106 exploit?

CVE-2026-9106 exploits a UI misrepresentation vulnerability that allows unauthorized organization runner management.

4

Who is affected by CVE-2026-9106?

CVE-2026-9106 affects users of GitHub Enterprise Server who use OAuth applications requesting the manage_runners:org scope.

5

What is the risk of not addressing CVE-2026-9106?

Failing to address CVE-2026-9106 may allow attackers to gain unauthorized access to manage organization runners.

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