CVE-2026-9106

MEDIUMNVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-06-30. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.5
EG Score
5.5(high)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
11.0%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 2, 2026

Advisory Details (5)

Auto-updated Jun 30, 2026
No patch confirmed yet.
generic

Release notes - GitHub Enterprise Server 3.21 Docs

https://docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.2
generic

Release notes - GitHub Enterprise Server 3.20 Docs

https://docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.4
generic

Release notes - GitHub Enterprise Server 3.19 Docs

https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.8
generic

Release notes - GitHub Enterprise Server 3.18 Docs

https://docs.github.com/en/enterprise-server@3.18/admin/release-notes#3.18.11
generic

Release notes - GitHub Enterprise Server 3.17 Docs

https://docs.github.com/en/enterprise-server@3.17/admin/release-notes#3.17.17

Vendor 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 10× in last 7d / 47× 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.

  1. 2026-07-23 03:23 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 17:56 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-15 18:14 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 18:31 UTCGHSA enrichment
  15. 2026-07-13 22:31 UTCEPSS rescore
  16. 2026-07-13 18:49 UTCGHSA enrichment
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-12 19:07 UTCGHSA enrichment
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-11 19:25 UTCGHSA enrichment
  21. 2026-07-11 08:27 UTCEPSS rescore
  22. 2026-07-10 19:43 UTCGHSA enrichment
  23. 2026-07-09 20:01 UTCGHSA enrichment
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-08 20:18 UTCGHSA enrichment
Show 22 more
  1. 2026-07-08 15:16 UTCEPSS rescore
  2. 2026-07-07 20:34 UTCGHSA enrichment
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-06 20:51 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-05 21:09 UTCGHSA enrichment
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 21:26 UTCGHSA enrichment
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 21:44 UTCGHSA enrichment
  13. 2026-07-02 22:02 UTCEG score recompute▲ 0.70
  14. 2026-07-02 22:02 UTCGHSA enrichment
  15. 2026-07-02 16:57 UTCNVD updateCVSS v3 → 5.5
  16. 2026-07-01 22:19 UTCGHSA enrichment
  17. 2026-07-01 15:07 UTCEPSS rescore
  18. 2026-06-30 22:34 UTCEG score recompute▲ 4.80
  19. 2026-06-30 22:34 UTCGHSA enrichment
  20. 2026-06-30 22:33 UTCNVD updateCVSS v3 → 4.8 · CVSS v4 → 4.8
  21. 2026-06-30 22:31 UTCEG score recompute
  22. 2026-06-30 22:31 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-9106?
CVE-2026-9106 is a medium vulnerability published on June 30, 2026. 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…
When was CVE-2026-9106 disclosed?
CVE-2026-9106 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9106 actively exploited?
CVE-2026-9106 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9106?
CVE-2026-9106 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-9106?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9106, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9106

Explore →

Is Your Infrastructure Affected by CVE-2026-9106?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs