CVE-2026-5512
4.3 · MEDIUMOverview
CVE-2026-5512 is a medium-severity vulnerability affecting github enterprise_server. It was published on April 21, 2026 and has a CVSS 3.1 base score of 4.3 (MEDIUM).
This vulnerability has a CVSS 3.1 base score of 4.3, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
Technical Description
An improper authorization vulnerability was identified in GitHub Enterprise Server that allowed an authenticated attacker to determine the names of private repositories by their numeric ID. The mobile upload policy API endpoint did not perform an early authorization check, and validation error messages included the full repository name for repositories the caller did not have access to. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.20.1, 3.19.5, 3.18.8, 3.17.14, 3.16.17, 3.15.21, and 3.14.26. This vulnerability was reported via the GitHub Bug Bounty program.
Remediation
Check the references section for vendor advisories and patches from github. Update enterprise_server to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| github | enterprise_server | >= 0, < 3.14.26 | Affected |
References
Frequently Asked Questions
What is CVE-2026-5512?
CVE-2026-5512 is a medium-severity vulnerability affecting github enterprise_server. It was published on April 21, 2026 and has a CVSS 3.1 base score of 4.3 (MEDIUM).
How severe is CVE-2026-5512?
This vulnerability has a CVSS 3.1 base score of 4.3, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2026-5512?
Check the references section for vendor advisories and patches from github. Update enterprise_server to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2026-5512?
CyberStrike's AI-powered security agents can automatically detect CVE-2026-5512 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related MEDIUM CVEs from 2026
View all →Discourse is an open source discussion platform. In versions prior to 3.5.4, 2025.11.2, 2025.12.1, a
In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize
Buffer overflow vulnerability in the HDC module. Impact: Successful exploitation of this vulnerabili
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior
A improper certificate validation vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.4, Forti
OpenClaw versions prior to 2026.3.1 fail to properly handle authentication bootstrap errors during s
File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing
Vulnerability of improper permission control in the theme setting module. Impact: Successful exploit
Access of resource using incompatible type ('type confusion') vulnerability in Samsung Open Source E
A flaw was found in Keycloak, specifically in the organization selection login page. A remote attack
Serendipity is a PHP-powered weblog engine. In versions 2.6-beta2 and below, the serendipity_setCoo
In iTerm2 through 3.6.9, displaying a .txt file can cause code execution via DCS 2000p and OSC 135 d