CVE-2026-117646 json
Gitea private repository listing to public-only tokens on profiles
published 2026-11-01 8 d ago modified 2026-11-06 3 d ago also EUVD-2026-114798
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Gitea Gitea 28.3.0
- github.com/go-gitea/gitea#39690 pull request
- github.com/go-gitea/gitea#39853 pull request
- github.com/go-gitea/gitea/releases/tag/v28.3.0 release
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected products
- Gitea Gitea
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
github.com
/go-gitea/gitea/pull/39690
patch
-
github.com
/go-gitea/gitea/pull/39853
patch
-
github.com
/go-gitea/gitea/security/advisories/GHSA-wxcq-p34j-7cjj
vendor-advisory
-
blog.gitea.com
/release-of-28.3.0/
release-notes
-
github.com
/go-gitea/gitea/releases/tag/v28.3.0
release-notes
Sources
- CVE List CVE-2026-117646
- NVD CVE-2026-117646
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.