open source Gitea: security vulnerability (CVE-2026-73504)
Published Sources: BSI
What is affected, what to do
Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder Denial-of-Service-Zustände zu verursachen.
Update open source Gitea to version 1.27.3.
- Affected
- open source Gitea
< *..1.27.3
- open source Gitea
- Fixed in
- open source Gitea
1.27.3
- open source 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.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Reserved
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- 65.33 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
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
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- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
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
Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder Denial-of-Service-Zustände zu verursachen.
Source: BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Open Source | Gitea |
|
|
Vendors and products
Included in the same advisory
| Medium | CVE-2026-78433 | Gitea private attachment disclosure through repository mismatch | 5.9 | — |
| Medium | CVE-2026-73273 | Gitea Maven checksum upload quota bypass and memory exhaustion | 4.3 | — |
| Medium | CVE-2026-73135 | Gitea hidden-owner repository listing disclosure | 5.3 | — |
| Medium | CVE-2026-73130 | Gitea repository initialization resource exhaustion | 4.3 | — |
| Medium | CVE-2026-73126 | Gitea private workflow badge token scope bypass | 4.3 | — |
| Medium | CVE-2026-71301 | Gitea private pull request title disclosure through markup | 4.3 | — |
| High | CVE-2026-71184 | Gitea fork workflow approval bypass through review events | 8.8 | — |
| Medium | CVE-2026-70407 | Gitea organization listing token scope bypass | 4.3 | — |
| Medium | CVE-2026-70406 | Gitea private comparison disclosure with public-only tokens | 6.5 | — |
| Medium | CVE-2026-70402 | Gitea local code execution through writable Git hooks | 5.8 | — |
| Medium | CVE-2026-70400 | Gitea private migration creation with public-only tokens | 5.4 | — |
| Medium | CVE-2026-70396 | Gitea organization repository creation token scope bypass | 5.4 | — |
| Medium | CVE-2026-68964 | Gitea restricted-user SSH and GPG key metadata disclosure | 4.3 | — |
| Medium | CVE-2026-68957 | Gitea restricted-user issue search disclosure | 4.3 | — |
| Medium | CVE-2026-67577 | Gitea restricted-user activity and heatmap disclosure | 4.3 | — |
| High | CVE-2026-66877 | Gitea fork workflow approval bypass through concurrency cancellation | 8.1 | — |
| Medium | CVE-2026-66874 | Gitea required Actions check bypass through skipped workflows | 6.5 | — |
| Medium | CVE-2026-66853 | Gitea restricted-user organization metadata disclosure | 4.3 | — |
| Medium | CVE-2026-66849 | Gitea restricted-user package visibility bypass | 4.3 | — |
| Medium | CVE-2026-63792 | Gitea private reusable workflow disclosure to fork runs | 5.3 | — |
| Medium | CVE-2026-63021 | Gitea Swift package manifest memory exhaustion | 6.5 | — |
| Medium | CVE-2026-62925 | Gitea Alpine package parsing memory exhaustion | 6.5 | — |
| Medium | CVE-2026-60021 | Gitea GitLab migration denial of service | 6.5 | — |
| Medium | CVE-2026-60018 | Gitea OneDev migration denial of service | 6.5 | — |
Show 1 more CVEs
| Medium | CVE-2026-60010 | Gitea organization team policy bypass through repository API | 6.5 | — |
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-73504"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-73504.svg?lang=en" alt="CVE-2026-73504 – NEOSEC Intel" height="20"></a>