CVE-2023-46646 json
Improper access control in all versions of GitHub Enterprise Server allows unauthorized users to view private repository names via the "Get…
published 2023-12-21 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-50848
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
Improper access control in all versions of GitHub Enterprise Server allows unauthorized users to view private repository names via the "Get a check run" API endpoint. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected GitHub Enterprise Server version 3.7.0 and above and was fixed in version 3.17.19, 3.8.12, 3.9.7 3.10.4, and 3.11.0.
Patch / fix
- GitHub Enterprise Server 3.7.19, 3.8.12, 3.9.7, 3.10.4, 3.11.0
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- GitHub Enterprise Server
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
docs.github.com
/en/enterprise-server@3.7/admin/release-notes#3.7.19
release-notes
-
docs.github.com
/en/enterprise-server@3.8/admin/release-notes#3.8.12
release-notes
-
docs.github.com
/en/enterprise-server@3.9/admin/release-notes#3.9.7
release-notes
-
docs.github.com
/en/enterprise-server@3.10/admin/release-notes#3.10.4
release-notes
Sources
- CVE List CVE-2023-46646
- NVD CVE-2023-46646
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.