Is code.gitea.io/gitea affected by CVE-2026-20912?

Go code.gitea.io/gitea is affected in <1.25.4.

Is CVE-2026-20912 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.4%.

medium

CVE-2026-20912

Q: Is CVE-2026-20912 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.4%.

Go · code.gitea.io/gitea • Go · github.com/go-gitea/gitea

Summary

Gitea does not properly validate repository ownership when linking attachments to releases in code.gitea.io/gitea

Severity: medium
EPSS: 0.4% (p28)
Also known as: GHSA-4xx9-vc8v-87hv, GHSA-vfmv-f93v-37mw, BIT-gitea-2026-20912, GO-2026-4364
Published: 2026-02-02

References

Related advisories

CVE-2026-28737 — high · Go/code.gitea.io/gitea
CVE-2026-24791 — high · Go/code.gitea.io/gitea
CVE-2026-22555 — high · Go/code.gitea.io/gitea
CVE-2026-26231 — high · Go/code.gitea.io/gitea
CVE-2026-28699 — high · Go/code.gitea.io/gitea
CVE-2026-28744 — high · Go/code.gitea.io/gitea
CVE-2026-20706 — medium · Go/code.gitea.io/gitea
CVE-2026-27783 — medium · Go/code.gitea.io/gitea

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.