CVE-2022-23738

published 1 Nov 2022 · updated 6 May 2025

Incomplete cache verification issue in GitHub Enterprise Server leading to exposure of private repo files

5.7MediumCVSS 5.7EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 3.2.20, 3.3.15, 3.4.10 and 2 more.

An improper cache key vulnerability was identified in GitHub Enterprise Server that allowed an unauthorized actor to access private repository files through a public repository. To exploit this, an actor would need to already be authorized on the GitHub Enterprise Server instance, be able to create a public repository, and have a site administrator visit a specially crafted URL. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.6 and was fixed in versions 3.2.20, 3.3.15, 3.4.10, 3.5.7, 3.6.3. This vulnerability was reported via the GitHub Bug Bounty program.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
GitHub>=3.2 <3.2.20, >=3.3 <3.3.15, >=3.4 <3.4.10, >=3.5 <3.5.7, >=3.6 <3.6.33.2.20, 3.3.15, 3.4.10, 3.5.7, 3.6.3

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-23738 severity on Zeptric[![CVE-2022-23738](https://zeptric.io/badge/cve/CVE-2022-23738.svg)](https://zeptric.io/cve/CVE-2022-23738)