GitHub Enterprise Server up to 3.17.16/3.18.10/3.19.7/3.20.3 REST API cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 2.64- |
Summary
A vulnerability, which was classified as problematic, has been found in GitHub Enterprise Server up to 3.17.16/3.18.10/3.19.7/3.20.3. This issue affects some unknown processing of the component REST API. The manipulation leads to cross site scripting. This vulnerability is uniquely identified as CVE-2026-10585. The attack is possible to be carried out remotely. No exploit exists. 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 and classified as problematic. This issue affects an unknown functionality of the component REST API. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:
A stored cross-site scripting vulnerability was identified in GitHub Enterprise Server that allowed an authenticated attacker to execute arbitrary JavaScript in another user's browser by injecting a crafted payload into the title of a Discussion in the Q&A category. The AnsweredQuestionStructuredDataComponent did not escape user-controlled Discussion titles before embedding them in a block, allowing the title to break out of the script context. The injection was escalated to a full cross-site scripting attack on GitHub Enterprise Server by leveraging JSONP callback support in the REST API to bypass the Content Security Policy. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.20.4, 3.19.8, 3.18.11, 3.17.17. This vulnerability was reported via the GitHub Bug Bounty program.
The weakness was disclosed by Seokchan Yoon (hamayanhamayan). It is possible to read the advisory at docs.github.com. The identification of this vulnerability is CVE-2026-10585 since 06/01/2026. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-2164). Statistical analysis made it clear that VulDB provides the best quality 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
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: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
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
06/01/2026 CVE reserved07/01/2026 Advisory disclosed
07/01/2026 VulDB entry created
07/01/2026 VulDB entry last update
Sources
Advisory: docs.github.comResearcher: Seokchan Yoon (hamayanhamayan)
Status: Confirmed
CVE: CVE-2026-10585 (🔒)
GCVE (CVE): GCVE-0-2026-10585
GCVE (VulDB): GCVE-100-375467
CERT Bund: WID-SEC-2026-2164 - Microsoft GitHub Enterprise Server: Mehrere Schwachstellen
Entry
Created: 07/01/2026 10:37Updated: 07/01/2026 13:44
Changes: 07/01/2026 10:37 (69), 07/01/2026 13:44 (7)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.