CVE-2025-6600: GitHub Enterprise Server Information Disclosure Vulnerability Exposes Private Repository Names via Search API
An exposure of sensitive information vulnerability was identified in GitHub Enterprise Server that could allow an attacker to disclose the names of private repositories within an organization. This issue could be exploited by leveraging a user-to-server token with no scopes via the Search API endpoint. Successful exploitation required an organization administrator to install a malicious GitHub App in the organization’s repositories. This vulnerability impacted only GitHub Enterprise Server version 3.17 and was addressed in version 3.17.2. The vulnerability was reported through the GitHub Bug Bounty program.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.17.2
Event History
Frequently Asked Questions
What is the severity of CVE-2025-6600?
CVE-2025-6600 is considered a medium severity vulnerability due to its potential to expose sensitive information.
How do I fix CVE-2025-6600?
To mitigate CVE-2025-6600, update GitHub Enterprise Server to a version that is not affected by this vulnerability.
What type of data can be disclosed by exploiting CVE-2025-6600?
Exploitation of CVE-2025-6600 can disclose the names of private repositories within an organization.
Who is affected by CVE-2025-6600?
Organizations using GitHub Enterprise Server are affected by CVE-2025-6600.
What type of attack leverages CVE-2025-6600?
CVE-2025-6600 can be exploited by leveraging a user-to-server token with no scopes.