Live › vulnerability › CVE-2026-118504
Several Gitea REST API issue routes skip the archived-repository check that the web interface applies. A user with rights to an archived repository can edit, close or delete issues, change labels, time tracking and pins there, altering data archiving should freeze.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-01 10:49 UTC. All times on this page are UTC.
Only Gitea instances that host archived repositories and have users with write access to them. The web interface already blocks these changes, so the exposure is through the REST API. Instances without archived repositories, or where only trusted users can write, are less exposed.
No product ranges from the sources yet.
gitea --version or check the version shown in the admin dashboard; versions below 28.3.0 are in scope28.3.0 or later (the sources say 28.2.0 fixed only some routes)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-118504")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.