code.gitea.io/gitea
Affected
- introduced
0, fixed1.27.0(semver)
Fixed versions
1.27.0
Fix
- Fixed version
1.27.0go get code.gitea.io/[email protected]
Advisory
Also known as: CVE-2026-58434, GO-2026-6062
Gitea: Private Repository Metadata Remains Accessible After Access Revocation
Summary
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.
Details
The issue affects the authenticated endpoint:
GET /api/v1/user/starred
The same behavior was also observed on:
GET /api/v1/user/subscriptions
A reproducible scenario is:
alice creates a private repository.bob is granted collaborator access.bob stars the repository.alice removes bob from the repository collaborators.bob is denied.bob requests /api/v1/user/starred.Additionally, if repository metadata is modified after access revocation, the updated values are returned by /api/v1/user/starred.
As a result, a user who no longer has permission to access the repository can continue to obtain repository metadata through the starred repository list.
PoC
PoC Link
https://anonymous.4open.science/r/Gitea_PoC-EC93/5_poc_starred_list
PoC Details
alice/P
description = "INITIAL"
bob as a collaborator with read access.bob, star the repository:PUT /api/v1/user/starred/alice/P
Response:
204 No Content
bob from the collaborator list.description = "AFTER-REVOKE"
GET /api/v1/repos/alice/P
Response:
404 Not Found
bob, request the starred repository list:GET /api/v1/user/starred
The response still contains the repository entry and reflects the updated description:
{
"full_name": "alice/P",
"description": "AFTER-REVOKE",
"private": true
}
This demonstrates that repository metadata remains accessible through the starred repository list even after repository access has been revoked.
Impact
A user who previously had legitimate access to a private repository can continue to retrieve repository metadata after losing access to the repository.
The exposed information includes repository metadata returned by the endpoint, such as:
full_name)private)This issue does not expose repository contents, source code, issues, pull requests, secrets, or collaborator information.
The impact is limited to continued access to repository metadata after repository permissions have been revoked.
Low Basis: The source's own band: LOW
0, fixed 1.27.0 (semver)1.27.0
1.27.0go get code.gitea.io/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0