# CVE-2025-8447: Incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed read-only access

> An attacker with repository access can read limited code from other private repositories by exploiting improper access controls in diff functionality.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-rw5q-23mh-r4c3

## What is CVE-2025-8447?

CVE-2025-8447 is a high-severity missing authorization vulnerability in Github Enterprise Server, published on 26 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An improper access control vulnerability was identified in GitHub Enterprise Server that allowed users with access to any repository to retrieve limited code content from another repository by creating a diff between the repositories. To exploit this vulnerability, an attacker needed to know the name of a private repository along with its branches, tags, or commit SHAs that they could use to trigger compare/diff functionality and retrieve limited code without proper authorization. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.18, and was fixed in versions 3.14.17, 3.15.12, 3.16.8 and 3.17.5. This vulnerability was reported via the GitHub Bug Bounty program.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Github Enterprise Server.

## How do I fix CVE-2025-8447?

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

## Is CVE-2025-8447 being exploited?

There is no known exploitation of CVE-2025-8447 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-8447 and fix it if it is affected.

What it is: CVE-2025-8447 is a high-severity missing authorization vulnerability in Github Enterprise Server, published on 26 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8447 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-8447/ (Markdown: https://insights.sbomify.com/CVE-2025-8447/index.md)
```

## Sources

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

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