CVE-2025-6600: GitHub Enterprise Server · Information Exposure
Affects GitHub Enterprise ServerSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GitHub GitHub Enterprise Server | Affected
| Fixed in– |
AI-suggested
European organizations should upgrade GitHub Enterprise Server instances from version 3.17.0 to 3.17.2 or later, where the vulnerability is patched. Administrators must enforce strict controls and vetting procedures for GitHub Apps installation, limiting installation rights to trusted personnel only. Implement monitoring and auditing of GitHub App installations and API usage to detect anomalous behavior indicative of exploitation attempts. Employ the principle of least privilege for tokens and API access, ensuring tokens have minimal scopes and are rotated regularly. Additionally, organizations should conduct internal security awareness training for administrators about the risks of installing untrusted applications. Network-level controls can be applied to restrict access to the GitHub Enterprise Server API endpoints to authorized IP ranges. Finally, maintain an incident response plan that includes procedures for handling suspected compromise of GitHub environments.
Description
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.