CVE-2026-0798
Low · 3.5CVSS
3.5
EPSS
0.3%
Published
Jan 23, 2026
CISA due date
—
The record
Gitea may send release notification emails for private repositories to users whose access has been revoked. When a repository is changed from public to private, users who previously watched the repository may continue to receive release notifications, potentially disclosing release titles, tags, and content.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Go | code.gitea.io/gitea | 0 | 1.25.4 |
| Bitnami | gitea | 0 | 1.25.4 |
| openSUSE:Leap 15.6 | govulncheck-vulndb | 0 | 0.0.20260205T172317-150000.1.146.1 |
Related vulnerabilities
- GO-2026-4365 Gitea may send release notification emails for private repositories to users whose access… Same vulnerability
- GO-2026-4363 Gitea does not properly validate repository ownership when deleting Git LFS locks in… Also affects code.gitea.io/gitea
- GO-2026-4364 Gitea does not properly validate repository ownership when linking attachments to… Also affects code.gitea.io/gitea
- GO-2026-4367 Gitea has improper access control for uploaded attachments in code.gitea.io/gitea Also affects code.gitea.io/gitea
- GO-2026-4368 Gitea improperly exposes issue titles and repository names through previously started… Also affects code.gitea.io/gitea
- GO-2026-4370 Gitea does not properly validate project ownership in organization project operations in… Also affects code.gitea.io/gitea
- GO-2026-4366 Gitea does not properly verify authorization when canceling scheduled auto-merges via the… Also affects code.gitea.io/gitea
- GO-2026-4369 Gitea does not properly validate ownership when toggling OpenID URI visibility in… Also affects code.gitea.io/gitea