Private Repository Metadata Remains Accessible After Access Revocation
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2026-58434
PublishedPrivate Repository Metadata Remains Accessible After Access Revocation
- Source published
- 13 Aug 2026 16:44:51 UTC
- Source modified
- 14 Aug 2026 17:22:41 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
euvd · EUVD-2026-58161
PublishedPrivate Repository Metadata Remains Accessible After Access Revocation
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Aug 13, 2026, 4:44:51 PM
dateUpdated: Aug 14, 2026, 5:22:41 PM
1 related source bulletins · separate from aliases
WID-SEC-W-2026-2304: Gitea: Mehrere Schwachstellen
CVE-2026-58417 · CVE-2026-58420 · CVE-2026-58425 · CVE-2026-58427 · CVE-2026-58428 · CVE-2026-58429 · CVE-2026-58431 · CVE-2026-58432 · CVE-2026-58433 · CVE-2026-58434 · CVE-2026-58435 · CVE-2026-58436 · CVE-2026-58437 · CVE-2026-58438 · CVE-2026-58439 · CVE-2026-58440 · CVE-2026-58441 · CVE-2026-58442 · CVE-2026-58443 · CVE-2026-58444 · CVE-2026-58445 · CVE-2026-58507 · CVE-2026-58508 · CVE-2026-58510 · CVE-2026-58511 · CVE-2026-59763 · CVE-2026-59765 · CVE-2026-59766 · CVE-2026-23603 · CVE-2026-42931 · CVE-2026-50105 · CVE-2026-54481 · CVE-2026-55982 · CVE-2026-55984 · CVE-2026-55986 · CVE-2026-55987 · CVE-2026-56443 · CVE-2026-56654 · CVE-2026-56657 · CVE-2026-56750 · CVE-2026-56755 · CVE-2026-57886 · CVE-2026-57894 · CVE-2026-57897 · CVE-2026-58314 · CVE-2026-58416
- Source published
- Aug 13, 2026, 4:44:51 PM (timezone not stated)
- Source modified
- Aug 14, 2026, 5:22:41 PM (timezone not stated)
- Saved here
- 19 Nov 2026 17:49:24 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd · CVE-2026-58434
PublishedPrivate Repository Metadata Remains Accessible After Access Revocation
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-200 · CWE-862
Original publisher date fields
published: 2026-08-13T17:17:27.377
lastModified: 2026-08-26T16:53:48.300
- Source published
- 13 Aug 2026 17:17:27 UTC
- Source modified
- 26 Aug 2026 16:53:48 UTC
- Saved here
- 25 Oct 2026 14:19:16 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
- Source published
- 21 Jul 2026 20:41:49 UTC
- Source modified
- 27 Jul 2026 17:11:16 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Publisher rating · LOW
osv · GO-2026-6062
PublishedGitea: Private Repository Metadata Remains Accessible After Access Revocation in gitea.dev
- Source published
- 27 Jul 2026 15:32:45 UTC
- Source modified
- 27 Jul 2026 17:00:25 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.