CVE-2026-116296None▾ TwilightPoC availableThe 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 rep…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 2.8 · likelihood 0.1 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 1 source. Availability, not in-the-wild use.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.3%
1 GitHub repo (last check)
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.
gitea.dev < 28.3.0Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-117649NoneGitea private issue disclosure through issue dependency timeline events
CVE-2026-119533NoneGitea private pull request disclosure on project boards
CVE-2026-118504NoneGitea issue changes on archived repositories through the API
CVE-2026-117677NoneGitea Helm chart upload decompression denial of service
CVE-2026-112887NoneGitea Actions task token private repository enumeration
CVE-2026-119627NoneGitea limited-visibility profile disclosure with public-only tokens