Gitea: GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private (CVE-2026-58510)
Gitea contains a vulnerability in its API path for changing repository visibility from public to private. When this change is made via the REST API, stale watch records are not cleared, allowing users who lost access to still see metadata of the now-private repository in their subscription list. This leads to exposure of repository metadata and inflated watcher counts. The issue affects versions from v1.25.4 up to but not including v1.27.0. The severity is medium with limited confidentiality impact and no integrity or availability impact.
AI Analysis
Technical Summary
The vulnerability in Gitea (CVE-2026-58510) arises from the API path used to edit repository visibility. Specifically, when a repository's visibility is changed from public to private via the REST API, the code path responsible for clearing watch records does not execute, resulting in stale watch entries remaining. Consequently, users who should no longer have access can still see metadata of the private repository in their watch subscription list. This flaw affects all versions from 1.25.4 up to but excluding 1.27.0. The vulnerability has a CVSS 3.1 score of 4.3 (medium severity) and impacts confidentiality only, without affecting integrity or availability. A patch is available that addresses this issue.
Potential Impact
Users who lose access to a repository due to its visibility change from public to private may still see metadata of that repository in their watch subscription list. This results in unintended exposure of repository metadata and inflated watcher counts. There is no impact on data integrity or service availability.
Mitigation Recommendations
A patch is available that fixes this issue in Gitea versions 1.27.0 and later. Users should upgrade to version 1.27.0 or newer to remediate this vulnerability. Since this is not a cloud service, remediation requires applying the patch or upgrading the affected software.
Gitea: GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private (CVE-2026-58510)
Description
Gitea contains a vulnerability in its API path for changing repository visibility from public to private. When this change is made via the REST API, stale watch records are not cleared, allowing users who lost access to still see metadata of the now-private repository in their subscription list. This leads to exposure of repository metadata and inflated watcher counts. The issue affects versions from v1.25.4 up to but not including v1.27.0. The severity is medium with limited confidentiality impact and no integrity or availability impact.
CVSS v3.1
Score 4.3medium
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
The vulnerability in Gitea (CVE-2026-58510) arises from the API path used to edit repository visibility. Specifically, when a repository's visibility is changed from public to private via the REST API, the code path responsible for clearing watch records does not execute, resulting in stale watch entries remaining. Consequently, users who should no longer have access can still see metadata of the private repository in their watch subscription list. This flaw affects all versions from 1.25.4 up to but excluding 1.27.0. The vulnerability has a CVSS 3.1 score of 4.3 (medium severity) and impacts confidentiality only, without affecting integrity or availability. A patch is available that addresses this issue.
Potential Impact
Users who lose access to a repository due to its visibility change from public to private may still see metadata of that repository in their watch subscription list. This results in unintended exposure of repository metadata and inflated watcher counts. There is no impact on data integrity or service availability.
Mitigation Recommendations
A patch is available that fixes this issue in Gitea versions 1.27.0 and later. Users should upgrade to version 1.27.0 or newer to remediate this vulnerability. Since this is not a cloud service, remediation requires applying the patch or upgrading the affected software.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-q423-49rw-g9mh
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-58510"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a600aa29c2644c7f8fdfcbf
Added to database: 07/22/2026, 00:11:14 UTC
Last enriched: 08/14/2026, 12:54:59 UTC
Last updated: 09/03/2026, 22:52:13 UTC
Views: 57
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.