# CVE-2026-131800: A stored cross-site scripting vulnerability was identified in GitHub Enterprise Server that allowed an organization member with permission t


- **Severity:** High 8.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-6hcf-3hg2-vpf9

## What is CVE-2026-131800?

CVE-2026-131800 is a high-severity vulnerability in GitHub Enterprise Server, published on 18 Nov 2026. 

### Official 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 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-131800?


## How do I fix CVE-2026-131800?

Upgrade GitHub Enterprise Server to the fixed version for your release line. The advisory names 3.23, 3.19.16, 3.20.12 and 3.21.10.

## Is CVE-2026-131800 being exploited?

There is no known exploitation of CVE-2026-131800 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-131800 and fix it if it is affected.

What it is: CVE-2026-131800 is a high-severity vulnerability in GitHub Enterprise Server, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-131800 in the wild and no public exploit code.

Affected product: GitHub Enterprise Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-131800/ (Markdown: https://insights.sbomify.com/CVE-2026-131800/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-131800
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-131800
- OSV: https://osv.dev/vulnerability/CVE-2026-131800

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-131800/
Summaries are generated and may contain mistakes; the official description above is the record.
