CVE
GitHub Enterprise Server authorization bypass exposes PR review threads
- Exploited
- No known exploitation
- Fix
- Fixed in 3.21.10, 3.22.5
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.21.10, 3.22.5.
Summary
GitHub Enterprise Server has a flaw that lets a logged-in user read review-thread data from private repositories they cannot access, including private file paths and, where diff data is available, source-code excerpts, commit identifiers, and line details. A remote attacker needs only a low-privilege account and no action from a victim, and reaches the flaw by supplying target thread identifiers to the thread-preview endpoint.
Original description
An authorization bypass through user-controlled key vulnerability was identified in GitHub Enterprise Server that allowed authenticated users to read review-thread data from private repositories they could not access. An attacker required an authenticated account, a readable repository and pull request to use as the request context, and target review-thread identifiers. The thread-preview endpoint resolved supplied identifiers without restricting them to the authorized pull request, exposing private file paths and, when positioning and diff data were available, source-code excerpts, commit identifiers, and line metadata without victim interaction. This vulnerability affected supported GitHub Enterprise Server releases in the 3.21, 3.22 series and was fixed in versions 3.21.10, 3.22.5. This vulnerability was reported via the GitHub Bug Bounty program.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.21.10, 3.22.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-111801 (Authorization bypass through user-controlled key vulnerability in GitHub Enterprise Server allowed disclosure of private pull request…), 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-111801 (entry last updated 2026-11-18):
Affected:
- GitHub Enterprise Server: from 3.21.0, fixed in 3.21.10; from 3.22.0, fixed in 3.22.5
Fixed versions: 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-111801 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-111801 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.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-111801
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-111801"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- GitHub Enterprise Server
From 3.21.0 · fixed in 3.21.10; From 3.22.0 · fixed in 3.22.5
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-111801 |
| Record | NVD · CVE-2026-111801 |
| Other links 2 | |
| Link | docs.github.com · en/enterprise-server@3.21/admin/release-notes#3.21.10 |
| Link | docs.github.com · en/enterprise-server@3.22/admin/release-notes#3.22.5 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111801
Is CVE-2026-111801 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: cve.now feed data
Which versions are affected by CVE-2026-111801?
Enterprise Server: from 3.21.0 before 3.21.10; from 3.22.0 before 3.22.5.Source: cve.now feed data
How do I fix CVE-2026-111801?
Upgrade to a fixed version: 3.21.10, 3.22.5.Source: cve.now feed data