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

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

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2025
- **Updated:** 1 Jul 2025
- **Also known as:** GHSA-mpx5-6w72-2g32

## 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 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-6600?

It affects 1 product.


Products: 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.

## Other vulnerabilities in Github Enterprise Server

- [CVE-2024-4985](https://insights.sbomify.com/CVE-2024-4985/): Auth bypass in Enterprise Server (critical 10.0)
- [CVE-2022-23739](https://insights.sbomify.com/CVE-2022-23739/): Missing authorization in GitHub Enterprise Server (critical 9.8)
- [CVE-2022-46255](https://insights.sbomify.com/CVE-2022-46255/): Improper Limitation of a Pathname to a Restricted Directory in GitHub Enterprise Server leading to RCE (critical 9.8)
- [CVE-2021-22869](https://insights.sbomify.com/CVE-2021-22869/): Improper access control in GitHub Enterprise Server allows self-hosted runners to execute outside their control group (critical 9.8)
- [CVE-2024-9487](https://insights.sbomify.com/CVE-2024-9487/): Auth bypass in Enterprise Server (critical 9.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6600 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2025-6600 in the wild and no public exploit code.

Affected product: Github Enterprise Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6600/ (Markdown: https://insights.sbomify.com/CVE-2025-6600/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6600
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6600
- OSV: https://osv.dev/vulnerability/CVE-2025-6600

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6600/
Summaries are generated and may contain mistakes; the official description above is the record.