CVE-2026-10585: CWE-79 Improper neutralization of input during web page generation ('cross-site scripting') in GitHub Enterprise Server
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 <script type="application/ld+json"> 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, 3.16.20. This vulnerability was reported via the GitHub Bug Bounty program.
AI Analysis
Technical Summary
This vulnerability in GitHub Enterprise Server involves improper neutralization of input during web page generation (CWE-79). An authenticated attacker can inject a crafted payload into the title of a Discussion in the Q&A category, which is not properly escaped before being embedded in a <script type="application/ld+json"> block. This allows the injected payload to break out of the script context. The attack is escalated to a full cross-site scripting exploit by leveraging JSONP callback support in the REST API to bypass the Content Security Policy. The vulnerability affects all versions prior to 3.21 and was fixed in versions 3.20.4, 3.19.8, 3.18.11, 3.17.17, and 3.16.20.
Potential Impact
An authenticated attacker can execute arbitrary JavaScript in the browsers of other users, potentially leading to session hijacking, unauthorized actions, or data exposure within the context of GitHub Enterprise Server. The vulnerability bypasses Content Security Policy protections via JSONP callback support, increasing the risk of successful exploitation.
Mitigation Recommendations
Fixes for this vulnerability are available in GitHub Enterprise Server versions 3.20.4, 3.19.8, 3.18.11, 3.17.17, and 3.16.20. Users should upgrade to these or later versions to remediate the issue. Since this is not a cloud service, remediation requires applying these official patches. Patch status is confirmed by the vendor advisory embedded in the description.
CVE-2026-10585: CWE-79 Improper neutralization of input during web page generation ('cross-site scripting') in GitHub Enterprise Server
Description
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 <script type="application/ld+json"> 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, 3.16.20. This vulnerability was reported via the GitHub Bug Bounty program.
CVSS v4.0
Score 6.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in GitHub Enterprise Server involves improper neutralization of input during web page generation (CWE-79). An authenticated attacker can inject a crafted payload into the title of a Discussion in the Q&A category, which is not properly escaped before being embedded in a <script type="application/ld+json"> block. This allows the injected payload to break out of the script context. The attack is escalated to a full cross-site scripting exploit by leveraging JSONP callback support in the REST API to bypass the Content Security Policy. The vulnerability affects all versions prior to 3.21 and was fixed in versions 3.20.4, 3.19.8, 3.18.11, 3.17.17, and 3.16.20.
Potential Impact
An authenticated attacker can execute arbitrary JavaScript in the browsers of other users, potentially leading to session hijacking, unauthorized actions, or data exposure within the context of GitHub Enterprise Server. The vulnerability bypasses Content Security Policy protections via JSONP callback support, increasing the risk of successful exploitation.
Mitigation Recommendations
Fixes for this vulnerability are available in GitHub Enterprise Server versions 3.20.4, 3.19.8, 3.18.11, 3.17.17, and 3.16.20. Users should upgrade to these or later versions to remediate the issue. Since this is not a cloud service, remediation requires applying these official patches. Patch status is confirmed by the vendor advisory embedded in the description.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_P
- Date Reserved
- 2026-06-01T19:08:05.407Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a443df227e9c79719767780
Added to database: 06/30/2026, 22:06:42 UTC
Last enriched: 07/08/2026, 12:27:46 UTC
Last updated: 08/14/2026, 00:41:09 UTC
Views: 88
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.