Gitea: Missing Authorization (CVE-2026-116296)
Published Sources: BSI
What is affected, what to do
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.
Update Gitea to version 28.3.0.
- Affected
- Gitea
lt *..28.3.0
- Gitea
- Fixed in
- Gitea
28.3.0
- Gitea
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
0.3 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 18.7
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.19 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.3 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 18.7
- Elevated — this CVE ranks above at least 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-862
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: BSI WID Portal
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Gitea | Gitea |
|
|
| Open Source | Gitea |
|
|
Vendors and products
Weakness classes (CWE)
CWE-862Missing Authorization
Class
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Entry at MITRE CWE-862
References & sources
- blog.gitea.comGitea 28.3.0 release announcementRelease notes
- github.comFix: go-gitea/gitea pull request #39690Patch
- github.comFix backport to release/v28: go-gitea/gitea pull request #39853Patch
- github.comFix: go-gitea/gitea pull request #39945Patch
- github.comFix backport to release/v28: go-gitea/gitea pull request #40115Patch
- github.comgo-gitea/gitea v28.3.0 releaseRelease notes
- github.comGitHub Security Advisory GHSA-5j4v-rwqr-vpq7Vendor advisory
- github.comGitHub Security Advisory GHSA-jr76-w9m3-3p68Vendor advisory
- github.comGitHub Security Advisory GHSA-8r36-6j2c-3gmvVendor advisory
- github.comGitHub Security Advisory GHSA-wxcq-p34j-7cjjVendor advisory
- github.comPartial fix (issue edit, delete and labels): go-gitea/gitea pull request #39839Patch
- github.comPartial fix backport to release/v28: go-gitea/gitea pull request #39847Patch
- github.comFix: go-gitea/gitea pull request #39942Patch
- github.comFix backport to release/v28: go-gitea/gitea pull request #40085Patch
- github.comGitHub Security Advisory GHSA-vmrc-8q2x-573xVendor advisory
- github.comGitHub Security Advisory GHSA-jh8p-x4ch-389qVendor advisory
- github.comGitHub Security Advisory GHSA-mf6p-vqpw-3r7xVendor advisory
- github.comGitHub Security Advisory GHSA-x5v4-836g-f95xVendor advisory
- github.comGitHub Security Advisory GHSA-8g99-g36h-5p2wVendor advisory
- github.comGitHub Security Advisory GHSA-3fv3-hhmm-4x2qVendor advisory
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
ReceivedGitea
Weakness type: CWE-862
Description added or changed
Show 8 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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.Weakness type (CWE) added —CWE-862Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/116xxx/CVE-2026-116296.json">CVE-2026-116296</a>Reference added —https://blog.gitea.com/release-of-28.3.0/Reference added —https://github.com/go-gitea/gitea/pull/39942Reference added —https://github.com/go-gitea/gitea/pull/40085Reference added —https://github.com/go-gitea/gitea/releases/tag/v28.3.0Reference added —https://github.com/go-gitea/gitea/security/advisories/GHSA-6h2f-c8jm-84hcSource identifier: 88ee5874-cf24-4952-aea0-31affedb7ff2
Linked CVEs
| Not rated | CVE-2026-119627 | Gitea limited-visibility profile disclosure with public-only tokens | — | — |
| Not rated | CVE-2026-119625 | Gitea user and organization feed token scope bypass | — | — |
| Not rated | CVE-2026-119533 | Gitea private pull request disclosure on project boards | — | — |
| Not rated | CVE-2026-119441 | Gitea public-only token bypass on bulk organization repository deletion | — | — |
| Not rated | CVE-2026-118504 | Gitea issue changes on archived repositories through the API | — | — |
| Not rated | CVE-2026-118395 | Gitea public-only token bypass in repository and organization creation | — | — |
| Not rated | CVE-2026-118394 | Gitea OAuth2 userinfo private group disclosure to public-only tokens | — | — |
| Not rated | CVE-2026-117685 | Gitea public-only package token access to private OCI blobs | — | — |
| Not rated | CVE-2026-117677 | Gitea Helm chart upload decompression denial of service | — | — |
| Not rated | CVE-2026-117649 | Gitea private issue disclosure through issue dependency timeline events | — | — |
| Not rated | CVE-2026-117646 | Gitea private repository listing to public-only tokens on profiles | — | — |
| Not rated | CVE-2026-117635 | Gitea admin API public-only token scope bypass | — | — |
| Not rated | CVE-2026-116474 | Gitea Actions job token spoofing of instance-signed commits | — | — |
| Not rated | CVE-2026-116296 | Gitea archived repository release, milestone and label modification | — | — |
| Not rated | CVE-2026-116289 | Gitea public-only token bypass through Actions runner registration | — | — |
| Not rated | CVE-2026-114199 | Gitea contribution heatmap private activity disclosure to public-only tokens | — | — |
| Not rated | CVE-2026-113429 | Gitea stored XSS through legacy Actions artifact Content-Encoding | — | — |
| Not rated | CVE-2026-112887 | Gitea Actions task token private repository enumeration | — | — |
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-116296"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-116296.svg?lang=en" alt="CVE-2026-116296 – NEOSEC Intel" height="20"></a>