Auth bypass in GitHub Enterprise Server
CVE-2026-15783
A missing authorization vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user with write access to any repository to read metadata from private repositories they did not have access to, including private repository owners and names, branch names, commit SHAs, commit messages, and the pushing actor. The delegated bypass endpoint resolved a rule suite directly from an attacker-supplied, encoded identifier without verifying that the requesting user could read the rule suite's repository, and because these identifiers are sequential an attacker could enumerate them across the instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.18, 3.18.12, 3.19.9, 3.20.5, and 3.21.3. This vulnerability was reported via the GitHub Bug Bounty program.
Vulnerability class: Broken Access Control
Published · last modified .
EPSS exploit prediction
EPSS: 0.004 (38.0th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 38th percentile — 38.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: 0.000
Affected products
- GitHub Enterprise Server — versions 3.17.0, 3.18.0, 3.19.0
Weakness classification (CWE)
References
- docs.github.com/en/enterprise-server@3.17/admin/release-notes (release-notes)
- docs.github.com/en/enterprise-server@3.18/admin/release-notes (release-notes)
- docs.github.com/en/enterprise-server@3.19/admin/release-notes (release-notes)
- docs.github.com/en/enterprise-server@3.20/admin/release-notes (release-notes)
- docs.github.com/en/enterprise-server@3.21/admin/release-notes (release-notes)