# CVE-2026-20800: Notification API Leaks Private Repository Issue Titles After Collaborator Permission Revocation

> Attackers with revoked access can view private repository issue titles via stale notifications, exposing sensitive metadata.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jan 2026
- **Updated:** 23 Jan 2026
- **Also known as:** BIT-gitea-2026-20800, GHSA-2vgv-hgv4-22mh, GHSA-g54m-9f6g-wj7q, GO-2026-4362

## What is CVE-2026-20800?

CVE-2026-20800 is a medium-severity vulnerability in Gitea Gitea, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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


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

Products: Gitea Gitea.

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

Upgrade github.com/go-gitea/gitea to 1.25.4 or later.

## Is CVE-2026-20800 being exploited?

There is no known exploitation of CVE-2026-20800 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-20800 and fix it if it is affected.

What it is: CVE-2026-20800 is a medium-severity vulnerability in Gitea Gitea, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-20800 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/go-gitea/gitea (Go): affected all versions; fixed in 1.25.4
- github.com/go-gitea/gitea (Go): affected all versions; fixed in 1.25.4
- gitea (Bitnami): affected all versions; fixed in 1.25.4
- code.gitea.io/gitea (Go): 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-20800/ (Markdown: https://insights.sbomify.com/CVE-2026-20800/index.md)
```

## Sources

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

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