Gitea private repository listing to public-only tokens on profiles
Affects Gitea 28.2.0 and earlier, where a public-only personal access token can see names of private repositories on profile, stars and watching tabs. Fixed in 28.3.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 8/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 28.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Gitea, the self-hosted Git service, is affected. A personal access token limited to public resources could be used to see names and metadata of private repositories, along with the owner's stars and watches on them, through user profile pages and organization home pages, though repository contents were not exposed.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
Caller uses a personal access token restricted to public resources (public-only). Affected Gitea versions are 28.2.0 and earlier, on the user profile repositories, stars and watching tabs and the organization equivalent.Upgrade to a fixed version: 28.3.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- gitea.dev
fixed in 28.3.0
Evidence 5
- Advisory
- Patch
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-117646
What does this mean?
A holder of a public-only personal access token can discover the names of private repositories visible to the token owner, plus that user's stars and watches of private repositories. Repository content is not disclosed.Source: github.com, blog.gitea.com
Am I affected, and how do I check?
Gitea 28.2.0 and earlier, on user profile repositories, stars and watching tabs, and the organization equivalents. Check the installed Gitea version and whether tokens are restricted to public resources.Source: github.com, blog.gitea.com
What should I do about it?
Upgrade to Gitea 28.3.0. No workaround is listed in the available facts.Source: github.com, blog.gitea.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data