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

Critical 9.1 Published Updated

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

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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, CWE-639, CWE-284

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.

PackageAffectedFixed in
github.com/go-gitea/gitea GoAll versions1.25.4
github.com/go-gitea/gitea GoAll versions1.25.4
gitea BitnamiAll versions1.25.4
code.gitea.io/gitea GoAll versions1.25.4

Products include Gitea Gitea.

How do I fix CVE-2026-20912?

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

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-20912 being exploited?

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

All Gitea Gitea vulnerabilities

Sources

Also known as BIT-gitea-2026-20912, GHSA-4xx9-vc8v-87hv, GHSA-vfmv-f93v-37mw, GO-2026-4364.

Is CVE-2026-20912 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free