Cross-repository access via revoked installation fallback
Published Apr 21, 2026 · Updated Apr 21, 2026
Improper authorization in GitHub Enterprise Server 3.14.0 through 3.20.0 allows remote authenticated users to access private repositories. Scoped user-to-server token authorization treats a revoked or deleted GitHub App installation as a global installation context instead of rejecting the token. Exploitation requires a scoped token and revocation timing or SSH push attribution, enabling repository reads and potentially writes outside the token's intended scope.
Summary
What happened
Improper authorization in GitHub Enterprise Server 3.14.0 through 3.20.0 allows remote authenticated users to access private repositories. Scoped user-to-server token authorization treats a revoked or deleted GitHub App installation as a global installation context instead of rejecting the token. Exploitation requires a scoped token and revocation timing or SSH push attribution, enabling repository reads and potentially writes outside the token's intended scope.
The record
- CVE
- CVE-2026-5845
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- Product
- GitHub Enterprise Server
- Classifications
- CWE-639, CAPEC-233, CAPEC-26, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.14.0 <=3.14.25 changes=[{"at":"3.14.26","status":"unaffected"}]
- Affected versionversion=3.15.0 <=3.15.20 changes=[{"at":"3.15.21","status":"unaffected"}]
- Affected versionversion=3.16.0 <=3.16.16 changes=[{"at":"3.16.17","status":"unaffected"}]
- Affected versionversion=3.17.0 <=3.17.13 changes=[{"at":"3.17.14","status":"unaffected"}]
- Affected versionversion=3.18.0 <=3.18.7 changes=[{"at":"3.18.8","status":"unaffected"}]
- Affected versionversion=3.19.0 <=3.19.4 changes=[{"at":"3.19.5","status":"unaffected"}]
- Affected versionversion=3.20.0 <3.20.1 changes=[{"at":"3.20.1","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo