CVE-2026-58434: Gitea: Private Repository Metadata Remains Accessible After Access Revocation
A user who previously had access to a private repository can continue to obtain repository metadata through GET /api/v1/user/starred after their access to the repository has been revoked.
After a collaborator is removed from a private repository, direct access to the repository is correctly denied. However, the repository may still appear in the user’s starred repository list, and the endpoint continues to return repository metadata. Changes made to that metadata after access revocation are also reflected in subsequent responses.
References
- github.com/advisories/GHSA-j2w3-9c3r-g83q
- github.com/go-gitea/gitea/commit/362539b78e50dfcc4bd1b9368fdd2a1b8cab0129
- github.com/go-gitea/gitea/commit/500a09e044156d7a8d6eb58d67a28b8a1512c887
- github.com/go-gitea/gitea/pull/38321
- github.com/go-gitea/gitea/pull/38390
- github.com/go-gitea/gitea/releases/tag/v1.27.0
- github.com/go-gitea/gitea/security/advisories/GHSA-j2w3-9c3r-g83q
- nvd.nist.gov/vuln/detail/CVE-2026-58434
Code Behaviors & Features
Detect and mitigate CVE-2026-58434 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →