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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/go-gitea/gitea/pull/39942 patch
- https://github.com/go-gitea/gitea/pull/40085 patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenunscored · giteaNVD modified 2026-11-01 09:48
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/go-gitea/gitea/security/advisories/GHSA-6h2f-c8jm-84hc vendor-advisory
- https://github.com/go-gitea/gitea/pull/39942 patch
- https://github.com/go-gitea/gitea/pull/40085 patch
- https://blog.gitea.com/release-of-28.3.0/ release-notes
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0 release-notes