CVE-2026-118504
Gitea issue changes on archived repositories through the API
CVSS Score
0.0
EPSS Score
0.0%
EPSS Percentile
0th
The web interface blocks issue and pull request changes on archived repositories, but several issue routes of the REST API did not check whether the repository is archived. A user allowed to change issues of an archived repository could use the API to edit, close or delete issues, change labels and deadlines, add or delete tracked time and stopwatches, add reactions, change issue blocks, and pin issues, altering data that archiving is meant to freeze. Gitea 28.2.0 added the check to the issue edit, delete and label routes; Gitea 28.3.0 applies it to all modifying repository API requests.
| Vendor | gitea |
| Product | gitea |
| Published | Nov 1, 2026 |
Stay Ahead of the Next One
Get instant alerts for gitea gitea
Be the first to know when new unknown vulnerabilities affecting gitea gitea are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
Affected Versions
Gitea / Gitea
0 < 28.3.0
References
github.com: https://github.com/go-gitea/gitea/security/advisories/GHSA-vmrc-8q2x-573x github.com: https://github.com/go-gitea/gitea/pull/39839 github.com: https://github.com/go-gitea/gitea/pull/39847 github.com: https://github.com/go-gitea/gitea/pull/39942 github.com: https://github.com/go-gitea/gitea/pull/40085 blog.gitea.com: https://blog.gitea.com/release-of-28.3.0/ github.com: https://github.com/go-gitea/gitea/releases/tag/v28.3.0
Credits
🔍 https://github.com/DevNoScope 🔍 https://github.com/nithissh7 https://github.com/bircni