CVE-2026-131800: Stored cross-site scripting vulnerability in GitHub Enterprise Server allowed unauthorized SSH key addition to another user account
A stored cross-site scripting vulnerability was identified in GitHub Enterprise Server that allowed an organization member with permission to manage custom-property definitions and edit property values to add an attacker-controlled SSH authentication key to the personal account of another member through HTML stored in a single-select custom-property option. Exploitation required another definition manager in the same organization to attempt to remove the poisoned option while it was in use and save the definition with a valid sudo session. Repository access through the added key depended on the permissions of the victim and independent authorization controls. This vulnerability affected supported GitHub Enterprise Server prior to 3.23 and was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. This vulnerability was reported via the GitHub Bug Bounty program.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.19.16 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.20.12 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.21.10 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.22.5
Event History
Frequently Asked Questions
Which GitHub Enterprise Server versions need remediation?
Supported GitHub Enterprise Server releases prior to 3.23 are affected. Fixes are available in 3.19.16, 3.20.12, 3.21.10, and 3.22.5.
What access does an attacker need to exploit this issue?
The attacker must be an organization member with permission to manage custom-property definitions and edit custom-property values. Exploitation also requires a second definition manager in the same organization to remove the poisoned option while it is in use and save the definition using a valid sudo session.
What is the practical impact if exploitation succeeds?
An attacker can add an attacker-controlled SSH authentication key to another organization member's personal account. Any repository access obtained through that key is limited by the victim's permissions and separate authorization controls.