CVE-2023-46646Network attack vector

Private repository-name disclosure via check-run authorization bypass

Published Dec 21, 2023 · Updated Nov 27, 2024

Improper access control in GitHub Enterprise Server allows remote attackers to read private repository names through its REST API. The Get a check run endpoint returns a private repository's name without enforcing the caller's repository access authorization. No authentication or user interaction is required, but disclosure is limited to the repository name and excludes repository content.

CVSS severity5.3
Medium
EPSS probability0.54%
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

Improper access control in GitHub Enterprise Server allows remote attackers to read private repository names through its REST API. The Get a check run endpoint returns a private repository's name without enforcing the caller's repository access authorization. No authentication or user interaction is required, but disclosure is limited to the repository name and excludes repository content.

The record

CVE
CVE-2023-46646
Published
Dec 21, 2023
Updated
Nov 27, 2024
Vendor
Twitter
Product
GitHub Enterprise Server
Classifications
CWE-639, T1213.003
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 21, 2023CVE publishedPublication date reported by the CVE source.
  2. Nov 27, 2024Record 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.10.0 <=3.10.3 changes=[{"at":"3.10.4","status":"unaffected"}]
  2. Affected versionversion=3.7.0 <=3.7.18 changes=[{"at":"3.7.19","status":"unaffected"}]
  3. Affected versionversion=3.8.0 <=3.8.11 changes=[{"at":"3.8.12","status":"unaffected"}]
  4. Affected versionversion=3.9.0 <=3.9.6 changes=[{"at":"3.9.7","status":"unaffected"}]

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Twitter · GitHub Enterprise Serverversion=3.10.0 <=3.10.3 changes=[{"at":"3.10.4","status":"unaffected"}]; version=3.7.0 <=3.7.18 changes=[{"at":"3.7.19","status":"unaffected"}]; version=3.8.0 <=3.8.11 changes=[{"at":"3.8.12","status":"unaffected"}]; version=3.9.0 <=3.9.6 changes=[{"at":"3.9.7","status":"unaffected"}]

Published CVSS scores

5.3GitHubCVSS:3.1/AV:N/AC:L/PR:N/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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-639Authorization Bypass Through User-Controlled Key
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