Description
An authorization bypass vulnerability was identified in GitHub Enterprise Server that allowed any authenticated user of the instance to read the raw diff or patch of pull requests in private repositories without authorization. Access tokens for raw pull request diffs and patches were scoped to the repository name and pull request number rather than to a globally unique repository identifier, so an attacker who created a repository and pull request matching a target's repository name and pull request number could use a token for their own repository to retrieve the private pull request's contents. Exploitation required the attacker to know the target repository's name and a valid pull request number. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.21, 3.18.15, 3.19.12, 3.20.8, and 3.21.6. This vulnerability was reported via the GitHub Bug Bounty program.
Published: 2026-09-22
Score: 6 Medium
EPSS: n/a
KEV: No
Impact: Unauthorized Data Access to Private Pull Request Diffs
Action: Patch Now
AI Analysis

Impact

An authorization bypass vulnerability in GitHub Enterprise Server lets any authenticated user read raw diffs or patches of pull requests in private repositories without permission. The flaw arises because tokens for these operations are scoped to the repository name and pull request number rather than a globally unique identifier, creating an opportunity for repository name collision to be exploited.

Affected Systems

The vulnerability affects GitHub Enterprise Server versions prior to 3.22. Specifically, versions 3.17, 3.18, 3.19, 3.20, and 3.21 are impacted, with the flaw fixed in releases 3.17.21, 3.18.15, 3.19.12, 3.20.8, and 3.21.6. Upgrading to 3.22 or later removes the issue.

Risk and Exploitability

The CVSS score is 6, indicating moderate severity. EPSS is not available and the vulnerability is not listed in the CISA KEV catalog, suggesting no known exploits in the wild. The attack requires legitimate authentication but permits unauthorized disclosure of confidential code changes through a repository name collision strategy, a relatively low‑skill path enabled by the insufficient authorization weakness (CWE‑639).

Generated by OpenCVE AI on September 22, 2026 at 22:35 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to GitHub Enterprise Server version 3.22 or later to apply the vendor fix.
  • Limit the use of raw diff and patch token scopes by adjusting repository‑level permissions or removing those scopes from users who do not require them.
  • Enforce strict naming conventions or implement pre‑creation reviews to prevent repository name collisions for private pull requests.

Generated by OpenCVE AI on September 22, 2026 at 22:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 22 Sep 2026 23:30:00 +0000

Type Values Removed Values Added
First Time appeared Github
Github enterprise Server
Vendors & Products Github
Github enterprise Server

Tue, 22 Sep 2026 21:00:00 +0000

Type Values Removed Values Added
Description An authorization bypass vulnerability was identified in GitHub Enterprise Server that allowed any authenticated user of the instance to read the raw diff or patch of pull requests in private repositories without authorization. Access tokens for raw pull request diffs and patches were scoped to the repository name and pull request number rather than to a globally unique repository identifier, so an attacker who created a repository and pull request matching a target's repository name and pull request number could use a token for their own repository to retrieve the private pull request's contents. Exploitation required the attacker to know the target repository's name and a valid pull request number. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.21, 3.18.15, 3.19.12, 3.20.8, and 3.21.6. This vulnerability was reported via the GitHub Bug Bounty program.
Title Authorization bypass vulnerability in GitHub Enterprise Server allowed reading of private pull request diffs and patches via repository name collision
Weaknesses CWE-639
References
Metrics cvssV4_0

{'score': 6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Github Enterprise Server
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_P

Published:

Updated: 2026-09-22T20:43:59.193Z

Reserved: 2026-08-17T17:21:03.791Z

Link: CVE-2026-75101

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-22T21:17:31.253

Modified: 2026-09-22T21:17:31.253

Link: CVE-2026-75101

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-22T23:15:15Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key