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.
CVE-2026-9106
Score 5.5 from GitHub Security Advisory published 2026-06-30. NVD baseline CVSS 5.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(high)
- EPSS
- 7.3%
- KEV
- Not listed
Published
June 30, 2026
Last Modified
July 2, 2026
Advisory Details (5)
Auto-updated Jun 30, 2026Release notes - GitHub Enterprise Server 3.21 Docs
https://docs.github.com/en/[email protected]/admin/release-notes#3.21.2Release notes - GitHub Enterprise Server 3.20 Docs
https://docs.github.com/en/[email protected]/admin/release-notes#3.20.4Release notes - GitHub Enterprise Server 3.19 Docs
https://docs.github.com/en/[email protected]/admin/release-notes#3.19.8Release notes - GitHub Enterprise Server 3.18 Docs
https://docs.github.com/en/[email protected]/admin/release-notes#3.18.11Release notes - GitHub Enterprise Server 3.17 Docs
https://docs.github.com/en/[email protected]/admin/release-notes#3.17.17Vendor Advisories for CVE-2026-9106(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 24× in last 7d / 24× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 20:51 UTCEG score recompute
- 2026-07-06 20:51 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-05 21:09 UTCEG score recompute
- 2026-07-05 21:09 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 21:26 UTCEG score recompute
- 2026-07-04 21:26 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 21:44 UTCEG score recompute
- 2026-07-03 21:44 UTCGHSA enrichment
- 2026-07-02 22:02 UTCEG score recompute▲ 0.70
- 2026-07-02 22:02 UTCGHSA enrichment
- 2026-07-02 16:57 UTCNVD updateCVSS v3 → 5.5
- 2026-07-01 22:19 UTCEG score recompute
- 2026-07-01 22:19 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 22:34 UTCEG score recompute▲ 4.80
- 2026-06-30 22:34 UTCGHSA enrichment
- 2026-06-30 22:33 UTCNVD updateCVSS v3 → 4.8 · CVSS v4 → 4.8
- 2026-06-30 22:31 UTCEG score recompute
- 2026-06-30 22:31 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-9106?
When was CVE-2026-9106 disclosed?
Is CVE-2026-9106 actively exploited?
What is the CVSS score of CVE-2026-9106?
How do I remediate CVE-2026-9106?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-9106
Is Your Infrastructure Affected by CVE-2026-9106?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.