CVE-2025-6600 GitHub Enterprise Server Information Disclosure Vulnerability Exposes Private Repository Names via Search API

Medium 6.3 Published Updated

An attacker can expose private repository names via the Search API if an admin installs a malicious GitHub App, requiring a patch to GitHub Enterprise Server.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-6600?

CVE-2025-6600 is a medium-severity vulnerability in Github Enterprise Server, published on 1 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-200

Which versions are affected by CVE-2025-6600?

It affects 1 product.

Products include Github Enterprise Server.

How do I fix CVE-2025-6600?

No fix has been published for CVE-2025-6600 yet. Limit exposure of the affected software until one is available.

Is CVE-2025-6600 being exploited?

There is no known exploitation of CVE-2025-6600 in the wild and no public exploit code.

All Github Enterprise Server vulnerabilities

Sources

Also known as GHSA-mpx5-6w72-2g32.

Is CVE-2025-6600 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free