Gitea: Private Repository Metadata Remains Accessible After Access Revocation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · 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 · score source

EPSS

• CVE-2026-58434: 0.47% estimated exploitation activity in the next 30 days; percentile 40.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: The same behavior was also observed on: 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…

Published by the source

21 Jul 2026, 20:41 UTC

Last modified by the source

21 Jul 2026, 20:41 UTC

Source last checked

26 Oct 2026, 15:27 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j2w3-9c3r-g83q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-58434

Advisory: Gitea: Private Repository Metadata Remains Accessible After Access Revocation
IDs: CVE-2026-58434, GHSA-j2w3-9c3r-g83q
Record: https://patchnext.com/advisories/cve-2026-58434 (revision 1, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: code.gitea.io/gitea 1.27.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go code.gitea.io/gitea: affected < 1.27.0; fixed in 1.27.0

## Suggested inspection (read-only)
- Go code.gitea.io/gitea: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on code.gitea.io/gitea.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j2w3-9c3r-g83q (GitHub-reviewed advisory GHSA-j2w3-9c3r-g83q lists affected ranges: Go code.gitea.io/gitea >=0 <1.27.0)

Commands are suggestions: review each one before running it.