Quick answers
- Is CVE-2026-116296 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116296 being exploited in the wild.
- How severe is CVE-2026-116296?
- Informational severity, published 1 November 2026.
- Which products and versions are affected?
- Gitea before 28.3.0.
- Is there a fix for CVE-2026-116296?
- Yes: fixed in Gitea 28.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116296 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116296?
- Check whether you run Gitea at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Gitea 28.3.0
Technical details
The vulnerability exists in Gitea's API routes for releases, release assets, milestones, and repository labels, which did not validate whether a repository was archived before allowing mutation operations. An authenticated user with write access to an archived repository, or a holder of such a user's write-scoped token, could bypass read-only enforcement to modify or delete release assets while preserving download URLs, delete releases and tags, and create/edit/delete milestones and labels. The fix adds validation to reject these operations with HTTP 423 Locked responses on archived repositories.
Affected products
- Gitea Gitea before 28.3.0
Timeline
- 2026-11-01: disclosed
- 2026-11-01: patched