CVE-2026-28740: CWE-639 in Gitea Gitea Open Source Git Server
Gitea versions up to and including 1.26.2 contain a vulnerability that allows Git LFS object reuse to improperly authorize access to private source objects. This affects users who have repository access but do not have Code-unit access, potentially exposing sensitive data. The vulnerability is identified as CWE-639 (Authorization Bypass Through User-Controlled Key) and CWE-863 (Incorrect Authorization).
AI Analysis
Technical Summary
CVE-2026-28740 affects Gitea Open Source Git Server versions up to 1.26.2. The vulnerability involves improper authorization checks related to Git LFS object reuse, allowing users with repository access but without Code-unit access to gain unauthorized access to private source objects. This is a case of authorization bypass due to insufficient validation of user permissions when reusing Git LFS objects. The CVSS 3.1 base score is 7.1, indicating a high severity issue with network attack vector, high attack complexity, low privileges required, no user interaction, and a scope change with high confidentiality impact, limited integrity impact, and no availability impact. There is no vendor advisory or patch information currently available, and no known exploits in the wild have been reported.
Potential Impact
The vulnerability allows unauthorized access to private source objects by users who should not have Code-unit access, potentially leading to exposure of sensitive code or data. The confidentiality impact is high, integrity impact is low, and availability is not affected. This could result in information disclosure within affected Gitea repositories.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch is currently documented, users should monitor Gitea vendor communications for updates. Until a fix is available, restrict repository access to trusted users and consider additional access controls or auditing to mitigate unauthorized access risks.
CVE-2026-28740: CWE-639 in Gitea Gitea Open Source Git Server
Description
Gitea versions up to and including 1.26.2 contain a vulnerability that allows Git LFS object reuse to improperly authorize access to private source objects. This affects users who have repository access but do not have Code-unit access, potentially exposing sensitive data. The vulnerability is identified as CWE-639 (Authorization Bypass Through User-Controlled Key) and CWE-863 (Incorrect Authorization).
CVSS v3.1
Score 7.1high
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
CVE-2026-28740 affects Gitea Open Source Git Server versions up to 1.26.2. The vulnerability involves improper authorization checks related to Git LFS object reuse, allowing users with repository access but without Code-unit access to gain unauthorized access to private source objects. This is a case of authorization bypass due to insufficient validation of user permissions when reusing Git LFS objects. The CVSS 3.1 base score is 7.1, indicating a high severity issue with network attack vector, high attack complexity, low privileges required, no user interaction, and a scope change with high confidentiality impact, limited integrity impact, and no availability impact. There is no vendor advisory or patch information currently available, and no known exploits in the wild have been reported.
Potential Impact
The vulnerability allows unauthorized access to private source objects by users who should not have Code-unit access, potentially leading to exposure of sensitive code or data. The confidentiality impact is high, integrity impact is low, and availability is not affected. This could result in information disclosure within affected Gitea repositories.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch is currently documented, users should monitor Gitea vendor communications for updates. Until a fix is available, restrict repository access to trusted users and consider additional access controls or auditing to mitigate unauthorized access risks.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Gitea
- Date Reserved
- 2026-03-03T03:25:59.982Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4820ff27e9c79719acc11a
Added to database: 07/03/2026, 20:52:15 UTC
Last enriched: 07/22/2026, 00:51:16 UTC
Last updated: 08/17/2026, 00:41:11 UTC
Views: 101
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.