Skip to content
Threat Brief

← All advisories

CVE-2026-131800

High 8.3No known exploitationFix available

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

Record last updated

CVSS score

8.3

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 31% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-79

Patching and mitigation

Patch status
Fix available (source: CVE record (GitHub_P))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
docs.github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
GitHubEnterprise Serverfrom 3.19.0 before 3.19.*Not documentedCVE Program
GitHubEnterprise Serverfrom 3.20.0 before 3.20.*Not documentedCVE Program
GitHubEnterprise Serverfrom 3.21.0 before 3.21.*Not documentedCVE Program
GitHubEnterprise Serverfrom 3.22.0 before 3.22.*Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by GitHub_P

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (GitHub_P)

    Source: CVE record (GitHub_P) (opens in a new tab)

Vendor guidance and references