dbcve.org
Enterprise ServerApplication · GitHub

CVE-2026-9106

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 3.16.20 / 3.17.17 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 manage_runners: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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A UI misrepresentation vulnerability in GitHub Enterprise Server allowed malicious OAuth applications to request the 'manage_runners:org' scope without displaying it on the authorization consent screen. This enabled attackers to gain unintended access to organization runner management by tricking users into authorizing an OAuth app.

MitigationUpgrade GitHub Enterprise Server to version 3.21.2, 3.20.4, 3.19.8, 3.18.11, 3.17.17, 3.16.20, or later. Review authorized OAuth applications in organizations for any suspicious apps with runner management permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise ServerApplication
Affected:< 3.16.20>= 3.17.0, < 3.17.17>= 3.18.0, < 3.18.11>= 3.19.0, < 3.19.8>= 3.20.0, < 3.20.4>= 3.21.0, < 3.21.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check GitHub Enterprise Server version
    Access the GitHub Enterprise Server admin console or run 'ghe-version' command from the management shell to determine the installed version.
    Affected if The installed version falls within any of these ranges: < 3.16.20; >= 3.17.0 and < 3.17.17; >= 3.18.0 and < 3.18.11; >= 3.19.0 and < 3.19.8; >= 3.20.0 and < 3.20.4; >= 3.21.0 and < 3.21.2.
  2. Review authorized OAuth applications at organization level
    Navigate to each organization's Settings > OAuth applications > Authorized OAuth Apps, or use the API to list authorized apps for organizations.
    Affected if Any OAuth application is authorized with permissions that include organization runner management capabilities.
  3. Inspect OAuth app scopes for manage_runners:org
    For each authorized OAuth app, examine the granted scopes in the application's authorization settings. Look specifically for the 'manage_runners:org' scope which grants organization runner management permissions.
    Affected if An OAuth application is authorized with the 'manage_runners:org' scope that was not visibly displayed to the user during authorization.
  4. Identify suspicious OAuth applications with runner permissions
    Review all OAuth applications that have been granted any runner-related scopes. Check for apps with unexpected names, unknown origins, or applications that request more permissions than their stated purpose would require.
    Affected if An OAuth application with runner management permissions exists that was authorized without clear user awareness of the full scope requested.

You are affected if your GitHub Enterprise Server version is within the affected ranges AND any OAuth application is authorized with the manage_runners:org scope without proper user disclosure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.16.20 / 3.17.17 / 3.18.11 or later
Fixed in 3.16.203.17.173.18.11
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.21.2, 3.20.4, 3.19.8, 3.18.11, 3.17.17, 3.16.20, or later. Review authorized OAuth applications in organizations for any suspicious apps with runner management permissions.

Recommended fix High confidence

Upgrade to version 3.21.2 or latest 3.x stable release (3.20.4, 3.19.8, 3.18.11, 3.17.17, or 3.16.20 based on your current branch)

  1. 1. Identify the current GitHub Enterprise Server version running in your environment
  2. 2. Based on the current version, upgrade to the corresponding fixed version: if < 3.16.20 upgrade to 3.16.20; if >= 3.17.0 and < 3.17.17 upgrade to 3.17.17; if >= 3.18.0 and < 3.18.11 upgrade to 3.18.11; if >= 3.19.0 and < 3.19.8 upgrade to 3.19.8
  3. 3. Test the upgrade in a staging environment before applying to production
  4. 4. After upgrade, verify that OAuth authorization consent screens now properly display the manage_runners:org scope
  5. 5. Review existing OAuth applications with runner permissions to ensure they are legitimate
Caveat Standard GitHub Enterprise Server upgrade considerations apply - review release notes for your target version for any configuration or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9106 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9106 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data