# CVE-2026-20912: Gitea: Cross-Repository Authorization Bypass via Release Attachment Linking Leads to Private Attachment Disclosure

> Attackers can link private repository attachments to public releases, exposing sensitive files to unauthorized users.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jan 2026
- **Updated:** 15 Jul 2026
- **Also known as:** BIT-gitea-2026-20912, GHSA-4xx9-vc8v-87hv, GHSA-vfmv-f93v-37mw, GO-2026-4364

## What is CVE-2026-20912?

CVE-2026-20912 is a critical missing authorization vulnerability in Gitea Gitea, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release in a different public repository, making it accessible to unauthorized users.

Weakness: CWE-283 (Unverified Ownership), CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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

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-20912?

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

## Is CVE-2026-20912 being exploited?

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

What it is: CVE-2026-20912 is a critical missing authorization vulnerability in Gitea Gitea, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-20912 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-20912/ (Markdown: https://insights.sbomify.com/CVE-2026-20912/index.md)
```

## Sources

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

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