| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00- |
Summary
A vulnerability categorized as problematic has been discovered in GitHub Enterprise Server up to 3.17.16/3.18.10/3.19.7/3.20.3/3.21.1. This affects an unknown function. Executing a manipulation can lead to clickjacking. This vulnerability is registered as CVE-2026-9106. It is possible to launch the attack remotely. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in GitHub Enterprise Server up to 3.17.16/3.18.10/3.19.7/3.20.3/3.21.1. It has been declared as problematic. This vulnerability affects an unknown functionality. The manipulation with an unknown input leads to a clickjacking vulnerability. The CWE definition for the vulnerability is CWE-451. The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks. As an impact it is known to affect integrity. CVE summarizes:
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. This vulnerability was reported via the GitHub Bug Bounty program.
The advisory is shared for download at docs.github.com. This vulnerability was named CVE-2026-9106 since 05/20/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1566.003.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-2164). Once again VulDB remains the best source for vulnerability data.
Affected
- Microsoft GitHub Enterprise
Product
Type
Vendor
Name
Version
- 3.17.0
- 3.17.1
- 3.17.2
- 3.17.3
- 3.17.4
- 3.17.5
- 3.17.6
- 3.17.7
- 3.17.8
- 3.17.9
- 3.17.10
- 3.17.11
- 3.17.12
- 3.17.13
- 3.17.14
- 3.17.15
- 3.17.16
- 3.18.0
- 3.18.1
- 3.18.2
- 3.18.3
- 3.18.4
- 3.18.5
- 3.18.6
- 3.18.7
- 3.18.8
- 3.18.9
- 3.18.10
- 3.19.0
- 3.19.1
- 3.19.2
- 3.19.3
- 3.19.4
- 3.19.5
- 3.19.6
- 3.19.7
- 3.20.0
- 3.20.1
- 3.20.2
- 3.20.3
- 3.21.0
- 3.21.1
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: ClickjackingCWE: CWE-451
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
05/20/2026 CVE reserved07/01/2026 Advisory disclosed
07/01/2026 VulDB entry created
07/01/2026 VulDB entry last update
Sources
Advisory: docs.github.comStatus: Confirmed
CVE: CVE-2026-9106 (🔒)
GCVE (CVE): GCVE-0-2026-9106
GCVE (VulDB): GCVE-100-375460
CERT Bund: WID-SEC-2026-2164 - Microsoft GitHub Enterprise Server: Mehrere Schwachstellen
Entry
Created: 07/01/2026 10:36Updated: 07/01/2026 13:44
Changes: 07/01/2026 10:36 (66), 07/01/2026 13:44 (7)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.