GitHub Enterprise Server up to 3.21.1 authorization

Summaryinfo

A vulnerability, which was classified as problematic, was found in GitHub Enterprise Server up to 3.21.1. Affected by this issue is some unknown functionality. Executing a manipulation can lead to authorization. This vulnerability is handled as CVE-2026-14340. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in GitHub Enterprise Server up to 3.21.1. This vulnerability affects some unknown functionality. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. As an impact it is known to affect integrity. CVE summarizes:

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.

The weakness was released by ahacker1. The advisory is available at docs.github.com. This vulnerability was named CVE-2026-14340 since 07/01/2026. The exploitation appears to be easy. The attack can be initiated remotely. The technical details are unknown and an exploit is not available.

Upgrading eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitHub

Name

• Enterprise Server

Version

• 3.16.0
• 3.16.1
• 3.16.2
• 3.16.3
• 3.16.4
• 3.16.5
• 3.16.6
• 3.16.7
• 3.16.8
• 3.16.9
• 3.16.10
• 3.16.11
• 3.16.12
• 3.16.13
• 3.16.14
• 3.16.15
• 3.16.16
• 3.16.17
• 3.16.18
• 3.16.19
• 3.17.0
• 3.17.1
• 3.17.2
• 3.17.3
• 3.17.4
• 3.17.5
• 3.17.6
• 3.17.7
• 3.17.8
• 3.17.9
• 3.17.10
• 3.17.11
• 3.17.12
• 3.17.13
• 3.17.14
• 3.17.15
• 3.17.16
• 3.18.0
• 3.18.1
• 3.18.2
• 3.18.3
• 3.18.4
• 3.18.5
• 3.18.6
• 3.18.7
• 3.18.8
• 3.18.9
• 3.18.10
• 3.19.0
• 3.19.1
• 3.19.2
• 3.19.3
• 3.19.4
• 3.19.5
• 3.19.6
• 3.19.7
• 3.20.0
• 3.20.1
• 3.20.2
• 3.20.3
• 3.21.0
• 3.21.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion