CVE-2025-11892: GitHub Enterprise Server · XSS or 'Cross-site Scripting'
Affects GitHub Enterprise ServerSource CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GitHub Enterprise Server | Affected
| Fixed in– |
AI-suggested
European organizations should immediately identify all GitHub Enterprise Server instances and verify their versions. Upgrading to the patched versions 3.18.1, 3.17.7, 3.16.10, 3.15.14, or 3.14.19 is essential to remediate the vulnerability. Until patching is complete, organizations should restrict sudo mode usage and educate users about the risks of clicking untrusted links, especially within the GitHub environment. Implementing strict access controls and monitoring for unusual workflow triggers or privilege escalations can help detect exploitation attempts. Network-level protections such as web filtering to block known malicious URLs and enhanced logging of user actions in GitHub Enterprise Server can provide additional defense layers. Regular security awareness training focused on phishing and social engineering can reduce the likelihood of successful user interaction exploitation. Finally, organizations should review and harden their GitHub Enterprise Server configurations to minimize attack surface exposure.
Description
An improper neutralization of input vulnerability was identified in GitHub Enterprise Server that allows DOM-based cross-site scripting via Issues search label filter that could lead to privilege escalation and unauthorized workflow triggers. Successful exploitation requires an attacker to have access to the target GitHub Enterprise Server instance and to entice a user, while operating in sudo mode, to click on a crafted malicious link to perform actions that require elevated privileges. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.18.1, 3.17.7, 3.16.10, 3.15.14, 3.14.19.
References
- docs.github.com/en/enterprise-server@3.18/admin/release-notes (opens in a new tab)
- docs.github.com/en/enterprise-server@3.17/admin/release-notes (opens in a new tab)
- docs.github.com/en/enterprise-server@3.16/admin/release-notes (opens in a new tab)
- docs.github.com/en/enterprise-server@3.15/admin/release-notes (opens in a new tab)
- docs.github.com/en/enterprise-server@3.14/admin/release-notes (opens in a new tab)