Skip to main content
VulnerabilityPublished

CVE-2026-131800: GitHub Enterprise Server · Cross-site Scripting

Affects GitHub Enterprise ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High · fixed in 3.22.5 : patch GitHub Enterprise Server soon.

Data as of 18 Nov 2026, 02:50 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_P)CVSS 4.08.3
Patch
Available – fixed in 3.22.5, 3.21.10, 3.20.12 +1
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Upgrade GitHub Enterprise Server to 3.22.5, 3.21.10, 3.20.12 or 3.19.16.

Affected software

ProductAffectedFixed in
GitHubEnterprise ServerAffected
  • >=3.22.0 <3.22.5
Fixed in
  • 3.22.5
GitHubEnterprise ServerAffected
  • >=3.21.0 <3.21.10
Fixed in
  • 3.21.10
GitHubEnterprise ServerAffected
  • >=3.20.0 <3.20.12
Fixed in
  • 3.20.12
GitHubEnterprise ServerAffected
  • >=3.19.0 <3.19.16
Fixed in
  • 3.19.16

AI-suggested

This vulnerability is fixed in GitHub Enterprise Server versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. Organizations should upgrade to these or later versions to remediate the issue. No additional mitigation actions are indicated by the vendor advisory.

Description

CVE-2026-131800 is a stored cross-site scripting (XSS) vulnerability in GitHub Enterprise Server that allowed an organization member with permissions to manage custom-property definitions to inject malicious HTML. This could lead to adding an attacker-controlled SSH authentication key to another member's personal account. Exploitation required a second definition manager to remove the poisoned option while it was in use and save the definition with a valid sudo session. The vulnerability affected versions prior to 3.19.16, 3.20.12, 3.21.10, and 3.22.5 and was fixed in those versions. Repository access via the added key depended on the victim's permissions and authorization controls. No known exploits in the wild have been reported.

References

Community reviews

Loading reviews…