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

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• github enterprise serverbefore 3.14.17
• github enterprise server3.15.0 and later · before 3.15.12
• github enterprise server3.16.0 and later · before 3.16.8
• github enterprise server3.17.0 and later · before 3.17.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_P). Independent of NVD's CPE analysis and usually ahead of it.

• GitHub Enterprise Server

  • 3.14 and later · up to and including 3.14.16affected · semverfixed in 3.14.17
  • 3.15 and later · up to and including 3.15.11affected · semverfixed in 3.15.12
  • 3.16 and later · up to and including 3.16.7affected · semverfixed in 3.16.8
  • 3.17 and later · up to and including 3.17.4affected · semverfixed in 3.17.5

Other highest-scoring records for the same primary product.

• CVE-2024-0200Unsafe Reflection in Github Enterprise Server leading to Command Injection
  61This week
• CVE-2024-0507Privilege Escalation by Code Injection in the Management Console in GitHub Enterprise Server
  55Plan
• CVE-2026-3854Remote code execution via git push option injection in GitHub Enterprise Server
  46Plan

Published before and after this one in the same product

• ← EarlierCVE-2025-6600Jul 1, 2025 · GitHub Enterprise Server Information Disclosure Vulnerability Exposes Private Repository Names via Search API
  25Monitor
• ← EarlierCVE-2025-6981Jul 15, 2025 · Incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed unauthorized read-only access
  21Monitor
• Later →CVE-2025-11578Nov 10, 2025 · Pre-Receive Hook Path Collision Vulnerability in GitHub Enterprise Server Allowing Privilege Escalation
  30Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1const invoice = await Invoice.findById(req.params.id);2res.json(invoice);

1const invoice = await Invoice.findOne({2  id: req.params.id,3  ownerId: req.user.id,4});5if (!invoice) return res.sendStatus(404);6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.