CVE-2026-97626 json
Gitea profile feed disclosure bypassing user visibility
published 2026-10-06 33 d ago modified 2026-10-07 32 d ago also EUVD-2026-94067
- 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
Requesting a user or organization profile page (`GET /{username}`) with an `Accept: application/rss+xml` or `Accept: application/atom+xml` header returned the owner's activity feed without the visibility check that the profile page and the `.rss` and `.atom` routes apply. Anonymous users, restricted users and non-members could confirm the existence of limited or private users and private organizations and read their profile details and public activity, also when `[other] ENABLE_FEED` was disabled. Activity in private repositories was not included.
Patch / fix
- github.com/go-gitea/gitea#39501 pull request
- github.com/go-gitea/gitea#39507 pull request
- github.com/go-gitea/gitea/releases/tag/v28.1.0 release
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 32 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
References
-
github.com
/go-gitea/gitea/pull/39501
patch
-
github.com
/go-gitea/gitea/pull/39507
patch
-
github.com
/go-gitea/gitea/security/advisories/GHSA-hf55-9cwq-2x64
vendor-advisory
-
blog.gitea.com
/release-of-28.1.0/
release-notes
-
github.com
/go-gitea/gitea/releases/tag/v28.1.0
release-notes
Sources
- CVE List CVE-2026-97626
- NVD CVE-2026-97626
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.