CVE-2026-116296 json
Gitea archived repository release, milestone and label modification
published 2026-11-01 8 d ago modified 2026-11-06 2 d ago also EUVD-2026-114795
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Gitea Gitea 28.3.0
- github.com/go-gitea/gitea#39942 pull request
- github.com/go-gitea/gitea#40085 pull request
- github.com/go-gitea/gitea/releases/tag/v28.3.0 release
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 d ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Gitea Gitea
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
github.com
/go-gitea/gitea/pull/39942
patch
-
github.com
/go-gitea/gitea/pull/40085
patch
-
github.com
/go-gitea/gitea/security/advisories/GHSA-6h2f-c8jm-84hc
vendor-advisory
-
blog.gitea.com
/release-of-28.3.0/
release-notes
-
github.com
/go-gitea/gitea/releases/tag/v28.3.0
release-notes
Sources
- CVE List CVE-2026-116296
- NVD CVE-2026-116296
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.