Skip to main content

Gitea CVE-2026-58423

| EUVDEUVD-2026-41606 HIGH
Improper Authentication (CWE-287)
2026-07-03 Gitea GHSA-7wvc-rvp7-w99x
7.7
CVSS 3.1 · Vendor: Gitea
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to Gitea SSH with low-priv account
  2. Delivery
    Send git-lfs-authenticate with malformed sub-verb
  3. Exploit
    Bypass repository authorization check
  4. Execution
    Obtain LFS read token for private repo
  5. Impact
    Exfiltrate private LFS objects

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires (1) a valid low-privileged authenticated Gitea account (CVSS PR:L - not unauthenticated), (2) network SSH access to the Gitea instance's Git-over-SSH endpoint, and (3) the target repositories using Git LFS, since the bypass is in the LFS git-lfs-authenticate SSH sub-verb parsing. The attacker triggers it by sending a malformed SSH sub-verb to obtain unauthorized LFS read access to private repositories. Limiting factors: it grants read-only confidentiality access (no write or code execution, I:N/A:N), it only exposes repositories/objects served via LFS, and it depends on the attacker already holding an account on the instance - so instances that disable open registration and restrict SSH reachability materially reduce exposure.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N, base 7.7 High) describes a network-reachable, low-complexity attack requiring only low privileges and no user interaction, yielding high confidentiality impact with a scope change - consistent with a valid low-privileged account reading data outside its authorization boundary. There is no EPSS score, SSVC decision, or KEV entry in the provided data, and POC availability is unknown, so exploitation-in-the-wild signals are absent; this reads as a real but not yet actively-exploited priority. The key limiting factor is PR:L: an attacker needs a valid Gitea account (or access to an instance that permits registration) and the ability to reach the SSH endpoint, which tempers mass-exploitation likelihood compared to a fully unauthenticated bug. There is no conflicting data, but note the impact is confidentiality-only (no write or code execution), so this is a data-exposure issue rather than a takeover.

Exploit ScenarioDerived

A user with only a low-privileged account on a shared Gitea instance connects over SSH and issues a git-lfs-authenticate request carrying a malformed sub-verb, causing Gitea to grant an LFS read token for a private repository they are not a member of. They then pull the private repository's LFS-stored objects, exfiltrating source code or secrets. No public POC is confirmed, and the low attack complexity means the request is straightforward to craft once the malformed-verb trick is known.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 03, 2026

Authentication bypass in Gitea's Git LFS (Large File Storage) SSH handling allows a low-privileged authenticated user to read files from private repositories they should not access by supplying a malformed SSH sub-verb, per the Gitea security advisory GHSA-7wvc-rvp7-w99x. Because the flaw crosses a security boundary (CVSS scope change) it exposes confidential repository contents without any integrity or availability impact. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV, but a vendor patch is available in Gitea 1.26.4.

RemediationAI

Vendor-released patch: Gitea 1.26.4 - upgrade all instances to 1.26.4 (or later) as documented in the release notes at https://github.com/go-gitea/gitea/releases/tag/v1.26.4 and the announcement at https://blog.gitea.com/release-of-1.26.3-and-1.26.4/, following the advisory at https://github.com/go-gitea/gitea/security/advisories/GHSA-7wvc-rvp7-w99x and PR https://github.com/go-gitea/gitea/pull/38008. If immediate patching is not possible, compensating controls include disabling Git LFS on the instance (trade-off: breaks LFS-backed repositories and large-file workflows), and restricting SSH access to the Gitea service to trusted networks or vetted accounts and disabling open self-registration so untrusted users cannot obtain the low-privileged account the exploit requires (trade-off: reduces convenience/self-service onboarding). Audit access logs for anomalous LFS-authenticate SSH activity against private repositories in the interim.

Affected VersionsENISA

Gitea Open Source Git Server 1.23.0 ≤1.26.2

Affected Packages

go code.gitea.io/gitea fix: 1.26.3
euvd gitea_open_source_git_server no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in go, 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 self-hosted Git service written in Go. The vulnerable component is its Git LFS transfer protocol handling over SSH: Gitea exposes LFS operations through SSH by parsing a sub-command/sub-verb passed alongside the git-lfs-authenticate flow. CWE-287 (Improper Authentication) is the root cause class - the SSH sub-verb parser fails to correctly validate or bind the requested LFS operation to the caller's authorization context, so a crafted/malformed sub-verb slips past the access-control check that normally restricts private-repository reads. The affected product per CPE is cpe:2.3:a:gitea:gitea_open_source_git_server, i.e. the Gitea Open Source Git Server across versions prior to the 1.26.4 fix.

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

Vendor (Gitea) PRIMARY 7.7 HIGH
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
vuln.today AI 7.7 HIGH

Network SSH access with a low-privileged account (PR:L), low complexity to craft the malformed sub-verb, scope change crossing the authorization boundary, and read-only exposure of private data (C:H, I/A:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
SUSE HIGH

Primary rating from Vendor (Gitea).

CVSS VectorVendor: Gitea

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

LFS authentication bypass via malformed SSH sub-verb allows unauthorized read access to private repositories

Executive ViewAI

Why It Matters

Gitea's Git LFS SSH handling contains an authentication bypass enabling low-privileged users to access confidential repository contents beyond their authorization. Although no public exploit has been identified at time of analysis, this exposure creates a data breach risk for organizations relying on Gitea to protect proprietary source code, intellectual property, and credentials. A vendor patch is available and should be deployed immediately.

Business Impact: High
Compensating Controls

Apply vendor patch (Gitea 1.26.4 or later). Until patching is complete, restrict SSH access to Git LFS operations at the network layer to limit exposure surface.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Medium
widely used self-hosted Git server, common but not ubiquitous in enterprises
Threat Intel
1
1 sources
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA Vendor CIRCL GitHub

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in Gitea

View all
CVE-2026-60004 CRITICAL POC
9.8

Remote code execution in Gitea (self-hosted Git service) via a code-injection flaw (CWE-94) allows attackers to run arbi

CVE-2026-27771 HIGH POC
8.2 Jul 03

Broken access control in Gitea's Composer package registry (versions up to and including 1.26.1) lets remote attackers r

CVE-2022-30781 HIGH POC
7.5 May 16

Gitea before 1.16.7 does not escape git fetch remote. Rated high severity (CVSS 7.5), this vulnerability is remotely exp

CVE-2020-14144 HIGH POC
7.2 Oct 16

The git hook feature in Gitea 1.1.0 through 1.12.5 might allow for authenticated remote code execution in customer envir

CVE-2024-6886 CRITICAL POC
10.0 Aug 06

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Gitea Gitea

CVE-2026-20896 CRITICAL POC
9.8 Jul 03

Reverse-proxy authentication bypass in the official Gitea Docker image (versions up to and including 1.26.2) allows any

CVE-2026-59774 CRITICAL POC
9.8

Path traversal in Gitea's Org-mode (`.org`) markup renderer allows an attacker who can get Org-mode content rendered by

CVE-2026-58053 CRITICAL POC
9.4 Jun 28

Container escape in Gitea act_runner (Docker backend, through act 0.262.0) lets an authenticated user with workflow-exec

CVE-2019-11229 HIGH POC
8.8 Apr 15

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

CVE-2026-57894 HIGH POC
8.5 Jul 21

Server-side request forgery and internal repository exfiltration in Gitea before 1.27.0 lets a low-privileged authentica

CVE-2026-24791 HIGH POC
8.1 Jun 17

Authorization bypass in Gitea versions 1.22.3 through 1.26.1 allows holders of `public-only` access tokens or OAuth gran

CVE-2020-13246 HIGH POC
7.5 May 20

An issue was discovered in Gitea through 1.11.5. Rated high severity (CVSS 7.5), this vulnerability is remotely exploita

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Server 16.1 Affected
SUSE Linux Enterprise Server for SAP applications 16.1 Affected
SUSE Linux Enterprise Module for Package Hub 15 SP5 Affected
SUSE Linux Enterprise Module for Package Hub 15 SP6 Affected
openSUSE Leap 15.5 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy