Live › vulnerability › CVE-2026-117646
Profile repository, star and watch tabs, and organization repository lists, ignored the public-only restriction on personal access tokens. A token holder could see names and metadata of private repositories visible to the token owner, but not their contents.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-01 10:49 UTC. All times on this page are UTC.
Exposure applies to people and organizations using fine-grained or classic personal access tokens restricted to public-only resources on GitHub. Teams running their own GitHub Enterprise instances should check the sources; the description does not say whether self-hosted versions are affected. Teams that do not use public-only tokens can likely skip it.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The repositories, stars and watching tabs of user profiles and the repository list of organization home pages included private repositories for every signed-in request without checking whether the request used a personal access token restricted to public resources (public-only). A holder of such a token could list the private repositories visible to the token's owner, and that user's stars and watches of private repositories. The API and the profile activity tab already applied the restriction. The impact is disclosure of repository names and metadata, not of repository content.
This page as .md · .json · in your agent: get_signal("CVE-2026-117646")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.