Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Private Repository Metadata Remains Accessible After Access Revocation

cve-program · severity unknownEUVD CVSS 3.1 7.5 CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary 7.5 HIGHCVSS_V4 Publisher rating LOWFixed by code.gitea.io/gitea 1.27.0osv · severity unknownFixed by gitea.dev 1.27.0KEV status unknown

cve-program · CVE-2026-58434

Published

Private Repository Metadata Remains Accessible After Access Revocation

Read the publisher's advisory

euvd · EUVD-2026-58161

Published

Private Repository Metadata Remains Accessible After Access Revocation

Read the publisher's advisory

nvd · CVE-2026-58434

Published

Private Repository Metadata Remains Accessible After Access Revocation

Read the publisher's advisory

osv · GHSA-j2w3-9c3r-g83q

Published

### 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: ```http GET /api/v1/user/starred ``` The same behavior was also observed on: ```http GET /api/v1/user/subscriptions ``` A reproducible scenario is: 1. User `alice` creates a private repository. 2. User `bob` is granted collaborator access. 3. `bob` stars the repository. 4. `alice` removes `bob` from the repository collaborators. 5. Direct repository access by `bob` is denied. 6. `bob` requests `/api/v1/user/starred`. 7. The repository is still present in the response together with repository metadata. 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 1. Create a private repository: ```text alice/P description = "INITIAL" ``` 2. Add `bob` as a collaborator with read access. 3. As `bob`, star the repository: ```http PUT /api/v1/user/starred/alice/P ``` Response: ```http 204 No Content ``` 4. Remove `bob` from the collaborator list. 5. Update the repository description: ```text description = "AFTER-REVOKE" ``` 6. Verify that direct repository access is no longer allowed: ```http GET /api/v1/repos/alice/P ``` Response: ```http 404 Not Found ``` 7. As `bob`, request the starred repository list: ```http GET /api/v1/user/starred ``` The response still contains the repository entry and reflects the updated description: ```json { "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: * Repository name (`full_name`) * Repository description * Repository visibility status (`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.

Read the publisher's advisory

osv · GO-2026-6062

Published

Gitea: Private Repository Metadata Remains Accessible After Access Revocation in gitea.dev

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2026-58434 · CVE overview and exploitation status

EUVD-2026-58161

GHSA-j2w3-9c3r-g83q

GO-2026-6062

cve-program · CVE-2026-58434

euvd · EUVD-2026-58161

nvd · CVE-2026-58434

osv · GHSA-j2w3-9c3r-g83q

osv · GO-2026-6062

Related changes

Linked by CVE identifier
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Nov 21:09 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current