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

> Gitea leaks private repository release details via email to users whose access was revoked after repository visibility changes.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Jan 2026
- **Updated:** 23 Jan 2026
- **Also known as:** BIT-gitea-2026-0798, GHSA-8fwc-qjw5-rvgp, GHSA-f4wq-6ww5-m56p, GO-2026-4365

## What is CVE-2026-0798?

CVE-2026-0798 is a low-severity vulnerability in Gitea Gitea, published on 22 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-0798?

4 open source packages ship an affected version, including code.gitea.io/gitea and gitea. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.gitea.io/gitea` | Go | All versions | 1.25.4 |
| `code.gitea.io/gitea` | Go | All versions | 1.25.4 |
| `code.gitea.io/gitea` | Go | All versions | 1.25.4 |
| `gitea` | Bitnami | All versions | 1.25.4 |

Products: Gitea Gitea.

## How do I fix CVE-2026-0798?

Upgrade code.gitea.io/gitea to 1.25.4 or later.

## Is CVE-2026-0798 being exploited?

There is no known exploitation of CVE-2026-0798 in the wild and no public exploit code.

## Other vulnerabilities in Gitea Gitea

- [CVE-2026-60004](https://insights.sbomify.com/CVE-2026-60004/): Gitea Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-73278](https://insights.sbomify.com/CVE-2026-73278/): Gitea WebAuthn bypass during OAuth and OIDC sign-in (critical 9.8)
- [CVE-2026-94205](https://insights.sbomify.com/CVE-2026-94205/): Gitea fork workflow approval bypass through maintainer-triggered events (critical 9.8)
- [CVE-2022-42968](https://insights.sbomify.com/CVE-2022-42968/): Gitea vulnerable to Argument Injection (critical 9.8)
- [CVE-2021-45330](https://insights.sbomify.com/CVE-2021-45330/): Improper Privilege Management in Gitea (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0798 and fix it if it is affected.

What it is: CVE-2026-0798 is a low-severity vulnerability in Gitea Gitea, published on 22 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-0798 in the wild and no public exploit code.

Affected packages and fixed versions:
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.25.4
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.25.4
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.25.4
- gitea (Bitnami): affected all versions; fixed in 1.25.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0798/ (Markdown: https://insights.sbomify.com/CVE-2026-0798/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0798
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0798
- OSV: https://osv.dev/vulnerability/CVE-2026-0798

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0798/
Summaries are generated and may contain mistakes; the official description above is the record.