Editing fine‑grained PAT resets repository access to 'All repositories'

[prateek]

Select Topic Area

Bug

Body

Summary
When editing an existing fine‑grained personal access token (PAT) that was originally scoped to specific repositories, the UI defaults to the 'All repositories' option instead of pre‑selecting the repositories originally chosen.

Steps to Reproduce

1. Create a fine‑grained personal access token with repository access limited to a specific repository (choose “Only select repositories” and pick a repository).
2. Save the token.
3. Navigate to the token’s settings page (e.g., https://github.com/settings/personal-access-tokens/10554559).
4. Click Edit to modify the token’s privileges.

Expected Behavior
The editor should remember the repositories that were originally selected and show those repositories in the “Selected repositories” list, so you can adjust permissions without changing the repository scope.

Actual Behavior
The editor defaults to “All repositories” under “Repository access”, effectively broadening the token’s scope. This happens even when the original token was restricted to one repository.

Impact
This bug makes it easy to accidentally grant a token access to all repositories, which defeats the purpose of fine‑grained scoping.

Environment

• GitHub web UI (tested on Chrome and Firefox, incognito mode, no extensions).
• Token created under personal user account.
• Issue observed on January 1, 2026.

Let me know if additional details are required.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[EricoEC]

same bug！

[LeaDevelop]

On initial token creation, selecting a single repository under "Only select repositories" does not fully restrict the token as expected. Git clone and API access are correctly limited to the selected repository however, the token can still list repositories beyond the selected scope, which it should not be able to do.

Proposed updated issue title:
fine-grained PAT repository selection not enforced on listing - token can enumerate repositories outside selected scope.

Clone and access appear to work correctly.
Even without write or clone access, repository enumeration is an information disclosure issue and should be tracked as a security-impacting (orgs) authorization bug imho.