Description
The API routes for releases, release assets, milestones and repository labels did not reject changes to archived repositories. A user with write access to an archived repository, or a holder of such a user's write-scoped token, could replace or delete release assets while keeping their download URLs, delete releases and tags, and create, edit or delete milestones and labels of a repository that is meant to be read-only. Changing requests on these routes now return 423 Locked for archived repositories.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Gitea | Gitea | < 28.3.0 | 28.3.0 |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
GitHub 1 repository
-
thalewalan/CVE-2026-116296 ★ 1 · Nov 1, 2026
Gitea archived repository write-protection bypass — milestones, releases and labels unprotected (CVE-2026-116296)
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
Advisories 1
- WID-SEC-2026-4281 Gitea: Mehrere Schwachstellen BSI CERT-Bund (WID) · Nov 1, 2026
References
- GitHub Security Advisory GHSA-6h2f-c8jm-84hc vendor-advisory
- Fix: go-gitea/gitea pull request #39942 patch
- Fix backport to release/v28: go-gitea/gitea pull request #40085 patch
- Gitea 28.3.0 release announcement release-notes
- go-gitea/gitea v28.3.0 release release-notes