CVE-2026-58435: CWE-266 in Gitea Gitea Open Source Git Server
Gitea LFS Deploy-Key Privilege Escalation
AI Analysis
Technical Summary
Gitea before version 1.27.0 contains a privilege escalation vulnerability (CVE-2026-58435) in its LFS deploy key handling. The flaw is due to a trust boundary confusion between authentication and authorization subsystems, where the system incorrectly assigns the repository owner's user ID to deploy keys in JWT tokens. This causes the LFS server to treat deploy key requests as if they come from the repository owner, enabling an attacker with write deploy key access to one repository to access LFS objects from any private repository owned by the same user, bypassing intended access restrictions.
Potential Impact
An attacker with write deploy key access to a single repository can escalate privileges to access LFS objects from any private repository owned by the same user. This bypasses intended access restrictions and may lead to unauthorized disclosure of private repository data. The impact is limited to confidentiality and integrity with no reported availability impact.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade to Gitea version 1.27.0 or later to remediate this issue. No additional mitigation steps are indicated by the vendor advisory.
CVE-2026-58435: CWE-266 in Gitea Gitea Open Source Git Server
Description
Gitea LFS Deploy-Key Privilege Escalation
CVSS v3.1
Score 5.4medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Gitea before version 1.27.0 contains a privilege escalation vulnerability (CVE-2026-58435) in its LFS deploy key handling. The flaw is due to a trust boundary confusion between authentication and authorization subsystems, where the system incorrectly assigns the repository owner's user ID to deploy keys in JWT tokens. This causes the LFS server to treat deploy key requests as if they come from the repository owner, enabling an attacker with write deploy key access to one repository to access LFS objects from any private repository owned by the same user, bypassing intended access restrictions.
Potential Impact
An attacker with write deploy key access to a single repository can escalate privileges to access LFS objects from any private repository owned by the same user. This bypasses intended access restrictions and may lead to unauthorized disclosure of private repository data. The impact is limited to confidentiality and integrity with no reported availability impact.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade to Gitea version 1.27.0 or later to remediate this issue. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-rh79-75qm-gwjr
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-58435"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a600ab19c2644c7f8fe1c92
Added to database: 07/22/2026, 00:11:29 UTC
Last enriched: 08/14/2026, 12:59:07 UTC
Last updated: 08/26/2026, 10:52:09 UTC
Views: 22
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.