CVE-2021-22863 | Improper access control in GitHub Enterprise Server leading to unauthorized changes to maintainer permissions on pull requests

An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would be able to gain access to head branches of pull requests opened on repositories of which they are a maintainer. Forking is disabled by default for organization owned private repositories and would prevent this vulnerability. Additionally, branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability affected all versions of GitHub Enterprise Server since 2.12.22 and was fixed in versions 2.20.24, 2.21.15, 2.22.7 and 3.0.1. This vulnerability was reported via the GitHub Bug Bounty program.

Published: 2021-03-02 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-22863 is rated Moderate Risk (53/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.97%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2021-22863

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.35% 0.97% +0.62%
2 2026-03-03 0.46% 0.35% -0.12%
3 2025-11-21 — 0.46% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-22863

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 5.2 [email protected]
5.5 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 8.0 4.9 [email protected]

Weakness enumeration for CVE-2021-22863

Affected software / configurations for CVE-2021-22863

Vendor Product Version Raw CPE
github github >= 2.12.22, < 2.20.24 cpe:2.3:a:github:github:*:*:*:*:enterprise:*:*:*
github github >= 2.21.0, < 2.21.15 cpe:2.3:a:github:github:*:*:*:*:enterprise:*:*:*
github github >= 2.22.0, < 2.22.7 cpe:2.3:a:github:github:*:*:*:*:enterprise:*:*:*
github github >= 3.0.0, < 3.0.1 cpe:2.3:a:github:github:*:*:*:*:*:*:*:*

References for CVE-2021-22863

cvelogic Threat Intelligence