CVE-2021-22863
No exploitation reported by the sources we read.
- Published2021-03-03
- Fixed in3.0.1 · 2.22.7 · 2.21.15 · 2.20.24
- WeaknessCWE-285
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2021-03-0304:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2021-22863?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-22863?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.0 | ≥ 3.0.0, < 3.0.1 | 3.0.1 | NVD |
| 2.22 | ≥ 2.22.0, < 2.22.7 | 2.22.7 | NVD |
| 2.21 | ≥ 2.21.0, < 2.21.15 | 2.21.15 | NVD |
| 2.x | ≥ 2.12.22, < 2.20.24 | 2.20.24 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Github to 3.0.1 · 2.22.7 · 2.21.15 · 2.20.24
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.18.1read 2026-10-23
- NVDCVSS 2.05.5read 2026-10-23
- CNAweakness (CWE)CWE-285read 2026-10-23
- FIRST EPSSEPSS score1.0 %2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Published
- 2021-03-03
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2021-22863?
Is CVE-2021-22863 actively exploited?
What is the CVSS score for CVE-2021-22863?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.