Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify unpatched Gitea instance
-
ExploitExploit unknown vulnerability
-
ImpactAchieve unknown impact
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation conditions cannot be determined from the available data. No CVSS vector, CWE, or vulnerability description was provided. The attack vector, required authentication level, user interaction requirements, and specific configuration triggers are all unknown. Defenders cannot assess realistic exploitation prerequisites beyond the fact that Gitea versions below 1.27.3 are affected. |
| Impact | Meaningful risk assessment is not possible from the available data. No CVSS vector, no CWE, no description of the vulnerability class, and no EPSS score or KEV listing are present in the intelligence sources. The only confirmed fact is that a security-relevant fix was applied to Gitea at the 1.27.3-r0 Alpine package level. Without knowing the attack vector, attack complexity, required privileges, or scope of impact, it is impossible to say whether this is a critical remote-code-execution flaw or a lower-severity information-disclosure issue. No public exploit has been identified at time of analysis. Defenders should treat the absence of detail as a reason to patch promptly rather than a reason to delay - unknown-severity vulnerabilities in self-hosted code-hosting infrastructure warrant conservative treatment. |
| Exploit ScenarioDerived | No exploit scenario can be responsibly constructed from the available data. The vulnerability class, affected component, attack vector, and required preconditions are all unknown. If the vulnerability proves to be remotely exploitable against default Gitea configurations, self-hosted instances exposed to the internet would represent the highest-risk targets. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 06, 2026
Gitea, the self-hosted Git service, received a security fix in Alpine Linux package version 1.27.3-r0. The upstream vulnerability details - including the specific weakness, affected component, and attack vector - are not disclosed in the available intelligence data. The Alpine Linux vendor advisory identifies the package correction but provides no CVE description, CWE classification, or CVSS scoring, making independent technical analysis of the vulnerability class impossible at this time.
RemediationAI
Upgrade the Alpine Linux gitea package to version 1.27.3-r0 or later using 'apk upgrade gitea'. For Gitea instances deployed outside Alpine Linux (Docker, binary, other distros), upgrade to upstream Gitea 1.27.3 or the latest stable release. Check the Gitea releases page and the official Gitea security advisories at https://github.com/go-gitea/gitea/security/advisories for the specific CVE details and any documented workarounds. Because the vulnerability class is unknown, no targeted compensating controls can be recommended - network-level restrictions (firewall rules limiting Gitea port exposure to trusted networks) are a generic precaution with the trade-off of limiting legitimate developer access. No specific workaround is confirmed from available data.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Gitea is a community-managed, lightweight self-hosted Git service written in Go, commonly deployed as an alternative to GitHub or GitLab in on-premises and private-cloud environments. The Alpine Linux package 'gitea' at version 1.27.3-r0 represents Gitea upstream version 1.27.3 packaged for Alpine (musl libc-based). No CWE is provided, so the root-cause class cannot be established from available data. CPE strings are absent from the input, preventing precise affected-version enumeration beyond what the Alpine package version implies.
Know when Gitea gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
Primary rating from Vendor (vendor:alpine) · only source for this CVE.
CVSS VectorVendor: vendor:alpine
Lifecycle Timeline
1DescriptionCVE.org
Alpine Linux: gitea fixed in 1.27.3-r0
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Remote code execution in Gitea (self-hosted Git service) via a code-injection flaw (CWE-94) allows attackers to run arbi
Broken access control in Gitea's Composer package registry (versions up to and including 1.26.1) lets remote attackers r
Gitea before 1.16.7 does not escape git fetch remote. Rated high severity (CVSS 7.5), this vulnerability is remotely exp
The git hook feature in Gitea 1.1.0 through 1.12.5 might allow for authenticated remote code execution in customer envir
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Gitea Gitea
Authenticated command injection in Dokploy (self-hostable PaaS) versions 0.29.3 through 0.29.12 lets a low-privileged us
Reverse-proxy authentication bypass in the official Gitea Docker image (versions up to and including 1.26.2) allows any
Path traversal in Gitea's Org-mode (`.org`) markup renderer allows an attacker who can get Org-mode content rendered by
Container escape in Gitea act_runner (Docker backend, through act 0.262.0) lets an authenticated user with workflow-exec
models/repo_mirror.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 mishandles mirror repo URL settings, leading to rem
Server-side request forgery and internal repository exfiltration in Gitea before 1.27.0 lets a low-privileged authentica
Authorization bypass in Gitea versions 1.22.3 through 1.26.1 allows holders of `public-only` access tokens or OAuth gran
EUVD-2026-101282
NVD
CVE.org
EPSS
GitHub
Exploit-DB