CVEsGiteaCVE-2026-117646Published Nov 1, 09:48 · Updated Nov 1, 09:48 UTC
–
Not scored
CVE-2026-117646

Gitea private repository listing to public-only tokens on profiles

gitea.dev
Affectedgitea.dev
FixUpdate to 28.3.0 or newer
PublishedNov 1, 09:48 · Gitea
ScoredNot yet
Exploit code publicNone known · checked 21:18 UTC
ExploitedNone known · CISA KEV checked 22:08 UTC

What we know

No known exploitation. CISA KEV, checked 22:08 UTC.
No public exploit code known. Exploit-DB, Metasploit, Nuclei, checked 21:18 UTC.
No severity score yet.

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.

From Gitea

Affected and fixed versions

ProductAffectedFixed ingitea.devbefore 28.3.028.3.0

Exploit code

Exploit-DBnone knownMetasploitnone knownNucleinone known

References

GitHub Security Advisory GHSA-wxcq-p34j-7cjj · github.comvendor advisoryFix: go-gitea/gitea pull request #39690 · github.compatchFix backport to release/v28: go-gitea/gitea pull request #39853 · github.compatchGitea 28.3.0 release announcement · blog.gitea.comrelease notesgo-gitea/gitea v28.3.0 release · github.comrelease notes

Other CVEs in gitea.dev

All 70 →
–Gitea limited-visibility profile disclosure with public-only tokens · CVE-2026-119627Nov 1–Gitea user and organization feed token scope bypass · CVE-2026-119625Nov 1–Gitea private pull request disclosure on project boards · CVE-2026-119533Nov 1