CVE-2026-131800: Stored cross-site scripting vulnerability in GitHub Enterprise Server allowed unauthorized SSH key addition to another user account

Published Nov 18, 2026
·
Updated

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

1 affected component
GitHub GitHub Enterprise Server<3.19.16, <3.20.12, <3.21.10, <3.22.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.19.16
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.20.12
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.21.10
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.22.5

Event History

Nov 18, 2026
CVE Published
via MITRE·02:34 AM
Data Sourced
via MITRE·02:34 AM
DescriptionWeakness
Data Sourced
via NVD·03:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203