Skip to main content
CVE-2025-8447VulnerabilityPublished

CVE-2025-8447: GitHub Enterprise Server · Insecure Direct Object Reference

Affects GitHub Enterprise ServerSource CVE Database V5

0

Not known to be exploited · CVSS 7.0 High · fixed in 3.14.17 : patch GitHub Enterprise Server soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.14.17
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHub Enterprise ServerAffected
  • =3.14
  • =3.15
  • =3.16
  • =3.17
Fixed in–

AI-suggested

European organizations should immediately verify their GitHub Enterprise Server versions and upgrade to the fixed releases (3.14.17, 3.15.12, 3.16.8, 3.17.5 or later). In addition to patching, organizations should audit repository access controls to ensure the principle of least privilege is enforced, limiting repository access strictly to necessary users. Monitoring and logging of repository compare/diff operations should be enhanced to detect anomalous or unauthorized attempts to access private repositories. Organizations should also review and rotate any credentials or secrets stored in repositories that might have been exposed. Implementing network segmentation to restrict access to GitHub Enterprise Server management interfaces and repositories can reduce exposure. Finally, conducting internal security awareness and training for developers and administrators about secure repository management and the risks of unauthorized data access is recommended.

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.

References

Community reviews

Loading reviews…