cve.bz

CVE-2026-9106 github enterprise server

4.8 mediumEPSS 0.4%Fix available

Medium (4.8) in github enterprise server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

4.8 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

5.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-07-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-451 User Interface (UI) Misrepresentation of Critical Information
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • GitHub Enterprise Server: fixed in 3.17.17
  • GitHub Enterprise Server: fixed in 3.18.11
  • GitHub Enterprise Server: fixed in 3.19.8
  • GitHub Enterprise Server: fixed in 3.20.4
  • GitHub Enterprise Server: fixed in 3.21.2
  • GitHub Enterprise Server: fixed in 3.16.20

Ask an AI about this CVE

Show the promptExplain CVE-2026-9106 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-9106?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-9106?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-9106 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GitHub Enterprise Serverfrom 3.17.0 through 3.17.16
GitHub Enterprise Serverfrom 3.18.0 through 3.18.10
GitHub Enterprise Serverfrom 3.19.0 through 3.19.7
GitHub Enterprise Serverfrom 3.20.0 through 3.20.3
GitHub Enterprise Serverfrom 3.21.0 through 3.21.1
GitHub Enterprise Serverfrom 3.16.0 through 3.16.19

Fixed in

ProductFixed in
GitHub Enterprise Server3.17.17
GitHub Enterprise Server3.18.11
GitHub Enterprise Server3.19.8
GitHub Enterprise Server3.20.4
GitHub Enterprise Server3.21.2
GitHub Enterprise Server3.16.20

Attack patterns (CAPEC)

  • CAPEC-98 Phishing Likelihood: High · Severity: Very High
  • CAPEC-154 Resource Location Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-163 Spear Phishing Likelihood: High · Severity: High
  • CAPEC-164 Mobile Phishing Likelihood: High · Severity: High
  • CAPEC-173 Action Spoofing Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON