Gitea archived repository release, milestone and label modification
Gitea 28.2.0 and earlier let users with write access to an archived repository change its releases, milestones and labels. Fixed in 28.3.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 28.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
Gitea, the self-hosted Git service, is affected. Users with write access to an archived (read-only) repository, or someone holding their write-scoped token, could modify or delete releases, release files, milestones, and labels in that repository, even though it should be locked from changes.
Read the original 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.
What to do
Upgrade to a fixed version: 28.3.0.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- gitea.dev
fixed in 28.3.0
Evidence 6
- Advisory
- Patch
- Patch
- Exploit
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116296
What does this mean?
An archived Gitea repository is meant to be read-only, but a user with write access to it can still modify its releases, milestones and labels.Source: github.com
Am I affected, and how do I check?
Gitea versions up to and including 28.2.0 are affected. The exposed setup is a write-level collaborator on the archived repository, or a write:repository API token belonging to such a user; default unit permissions include Releases and Issues write. Check the installed version with gitea --version.Source: github.com
What should I do about it?
Upgrade to Gitea 28.3.0 or later, which contains the patch.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data