Description
An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed a user-to-server token scoped to a GitHub App installation to perform certain write operations on public repositories outside the token's intended scope. This was possible because the authorization check only verified that the installation had read permissions on the target repository rather than verifying that the token's installation was explicitly granted access to that repository. An attacker who obtained a victim's user-to-server token could create issues, issue comments, commit comments, and private vulnerability reports on any public repository, appearing as the victim user with no indication of the app involvement. This vulnerability was fixed by adding a repository scope check for user-to-server tokens issued by global apps. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.21.2, 3.20.4, 3.19.8, 3.18.11, 3.17.17, 3.16.20. This vulnerability was reported via the GitHub Bug Bounty program.
Published: 2026-07-01
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

An incorrect authorization check in GitHub Enterprise Server, categorized as CWE‑863, allowed a user‑to‑server token issued to a GitHub App to perform write actions on any public repository that the app could read, even when the app was not explicitly granted access to that repository. The affected operations include creating issues, issue comments, commit comments, and private vulnerability reports. An attacker who obtained a victim’s token could produce these items under effectively enabling impersonation and defacement of public projects.

Affected Systems

The vulnerability applies to all releases of GitHub Enterprise Server before version 3.22. The advisory lists specific patched versions: 3.21.2, 3.20.4, 3.19.8, 3.18.11, 3.17.17, 3.16.20. Any instance running a pre‑3.22 release without these patches is susceptible.

Risk and Exploitability

The CVSS score of 5.3 places the issue at a moderate severity level. Based on the EPSS score of < 1%, it is inferred that exploitation is unlikely, but the lack of listing in the CISA KEV catalog suggests no widespread, publicly known exploits at this time. It is inferred that the a user‑to‑server token, which may be achieved through phishing, credential compromise, or abuse of a trusted GitHub App a token the attacker can freely write to any public repository that is readable by the app, presenting a moderate but tangible risk to confidentiality and integrity of project metadata.

Generated by OpenCVE AI on July 21, 2026 at 13:15 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the GitHub Enterprise Server to a patched release (3.21.2 or newer) to eliminate the vulnerability.
  • If an upgrade cannot be performed immediately, revoke or disable all global GitHub App installations that is updated.
  • Audit all existing GitHub App permissions, reduce scopes to the, and enforce explicit repository access or additional token validation checks to mitigate the CWE‑863 authorization bypass flaw.

Generated by OpenCVE AI on July 21, 2026 at 13:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 02 Jul 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 02 Jul 2026 04:00:00 +0000

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

Wed, 01 Jul 2026 21:15:00 +0000

Type Values Removed Values Added
Description An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed a user-to-server token scoped to a GitHub App installation to perform certain write operations on public repositories outside the token's intended scope. This was possible because the authorization check only verified that the installation had read permissions on the target repository rather than verifying that the token's installation was explicitly granted access to that repository. An attacker who obtained a victim's user-to-server token could create issues, issue comments, commit comments, and private vulnerability reports on any public repository, appearing as the victim user with no indication of the app involvement. This vulnerability was fixed by adding a repository scope check for user-to-server tokens issued by global apps. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.21.2, 3.20.4, 3.19.8, 3.18.11, 3.17.17, 3.16.20. This vulnerability was reported via the GitHub Bug Bounty program.
Title An incorrect authorization vulnerability in GitHub Enterprise Server allows issue creation in unrelated public repositories
Weaknesses CWE-863
References
Metrics cvssV4_0

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


Subscriptions

Github Enterprise Server
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_P

Published:

Updated: 2026-07-02T15:54:43.817Z

Reserved: 2026-07-01T13:42:35.041Z

Link: CVE-2026-14340

cve-icon Vulnrichment

Updated: 2026-07-02T15:10:44.207Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-21T13:30:07Z

Weaknesses