CVE-2022-46257Network attack vector

Private repository-name disclosure via runner-group API

Published Mar 7, 2023 · Updated Mar 6, 2025

Information disclosure in GitHub Enterprise Server 3.3 through 3.6 allows remote authenticated users to view private repository names. The runner-group API accepts an obfuscated private-repository ID from a user lacking repository access and then exposes the repository name in the UI. Exploitation requires access to the instance, permission to modify GitHub Actions runner groups, and a successful guess of the target repository's obfuscated ID.

CVSS severity4.3
Medium
EPSS probability0.57%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in GitHub Enterprise Server 3.3 through 3.6 allows remote authenticated users to view private repository names. The runner-group API accepts an obfuscated private-repository ID from a user lacking repository access and then exposes the repository name in the UI. Exploitation requires access to the instance, permission to modify GitHub Actions runner groups, and a successful guess of the target repository's obfuscated ID.

The record

CVE
CVE-2022-46257
Published
Mar 7, 2023
Updated
Mar 6, 2025
Vendor
Twitter
Product
GitHub Enterprise Server
Classifications
CWE-200, CWE-668, T1213.003
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Mar 7, 2023CVE publishedPublication date reported by the CVE source.
  2. Mar 6, 2025Record 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.

  1. Affected versionversion=3.3 <3.3.17
  2. Affected versionversion=3.4 <3.4.12
  3. Affected versionversion=3.5 <3.5.9
  4. Affected versionversion=3.6 <3.6.5

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Twitter · GitHub Enterprise Serverversion=3.3 <3.3.17; version=3.4 <3.4.12; version=3.5 <3.5.9; version=3.6 <3.6.5

Published CVSS scores

4.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
CWE-668Exposure of Resource to Wrong Sphere
T1213.003Data from Information Repositories: Code Repositories

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