CVE-2022-46257 | Information disclosure in GitHub Enterprise Server leading to unauthorized viewing of private repository names

An information disclosure vulnerability was identified in GitHub Enterprise Server that allowed private repositories to be added to a GitHub Actions runner group via the API by a user who did not have access to those repositories, resulting in the repository names being shown in the UI. To exploit this vulnerability, an attacker would need access to the GHES instance, permissions to modify GitHub Actions runner groups, and successfully guess the obfuscated ID of private repositories. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.7 and was fixed in versions 3.3.17, 3.4.12, 3.5.9, 3.6.5. This vulnerability was reported via the GitHub Bug Bounty program.

Published: 2023-03-07 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2022-46257 is rated Low Risk (32.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.57%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-46257

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.19% 0.57% +0.37%
2 2026-03-16 0.30% 0.19% -0.11%
3 2026-03-08 0.30%

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-46257

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 1.4 [email protected]

Weakness enumeration for CVE-2022-46257

Affected software / configurations for CVE-2022-46257

Vendor Product Version Raw CPE
github enterprise_server >= 3.3.0, < 3.3.17 cpe:2.3:a:github:enterprise_server:*:*:*:*:*:*:*:*
github enterprise_server >= 3.4.0, < 3.4.12 cpe:2.3:a:github:enterprise_server:*:*:*:*:*:*:*:*
github enterprise_server >= 3.5.0, < 3.5.9 cpe:2.3:a:github:enterprise_server:*:*:*:*:*:*:*:*
github enterprise_server >= 3.6.0, < 3.6.5 cpe:2.3:a:github:enterprise_server:*:*:*:*:*:*:*:*

References for CVE-2022-46257

cvelogic Threat Intelligence