CVE-2025-14046: 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, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% 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 11 Dec 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 upgrade GitHub Enterprise Server to versions 3.18.3, 3.17.9, 3.16.12, 3.15.16, or 3.14.21 or later, where the vulnerability is patched. Until patching is complete, implement strict content security policies (CSP) to restrict the execution of untrusted scripts and reduce the risk of XSS exploitation. Employ web application firewalls (WAFs) with custom rules to detect and block malicious payloads targeting this vulnerability. Enhance user awareness training focused on recognizing phishing and social engineering attempts that could deliver malicious content. Restrict access to GitHub Enterprise Server instances to trusted networks and users, minimizing exposure to untrusted actors. Monitor server logs and user activity for unusual POST requests or backend interactions that could indicate exploitation attempts. Consider deploying runtime application self-protection (RASP) solutions to detect and block anomalous DOM manipulations. Finally, review and harden project view configurations to limit the impact of DOM element collisions where feasible.
Description
An improper neutralization of input vulnerability was identified in GitHub Enterprise Server that allowed user-supplied HTML to inject DOM elements with IDs that collided with server-initialized data islands. These collisions could overwrite or shadow critical application state objects used by certain Project views, leading to unintended server-side POST requests or other unauthorized backend interactions. Successful exploitation requires an attacker to have access to the target GitHub Enterprise Server instance and to entice a privileged user to view crafted malicious content that includes conflicting HTML elements. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.18.3, 3.17.9, 3.16.12, 3.15.16, and 3.14.21.
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)