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-59766, GO-2026-6071
Gitea CVE-2026-20800 sibling endpoints not covered: revoked user still reads private repo objects via /api/v1/user/starred and private issue titles via /api/v1/user/times
Summary
CVE-2026-20800 fixed private-info leakage to revoked users only for the notification endpoint. Two
sibling endpoints that return data keyed on the caller's own relationship still do not re-check repo
access at output time:
GET /api/v1/user/starred — getStarredRepos() computes a per-repo permission but still lists every starred repo (no filtering), so the full repo object (full_name, private, clone_url, ssh_url) of a now-inaccessible private repo is returned.GET /api/v1/user/times — ListMyTrackedTimes() queries by UserID only and LoadAttributes brings in the issue (title, state), leaking private issue titles after revocation.Steps to reproduce
Using the provided reproduction materials, as a revoked user:
GET /api/v1/repos/admin/starred-test → 404.GET /api/v1/user/starred → leaks admin/starred-test, private:true, clone_url.GET /api/v1/user/times → leaks issue.title = "SECRET: …", state.(Runtime-confirmed on gitea/gitea:1.25.4. Oracle = planted sentinel title; no real secret exfiltrated.)
Impact
A former collaborator can enumerate private repos they starred and read private issue titles they logged
time on, indefinitely after access revocation. Metadata only (no repo content / comment bodies). Low.
Suggested remediation
getStarredRepos: drop (or minimally redact) repos where permission.HasAnyUnitAccessOrPublicAccess() is false for the caller.ListMyTrackedTimes: filter tracked-time entries by current repo access.Credit
Reported as part of an incomplete-patch measurement study (responsible disclosure).
Medium Basis: The source's own band: MODERATE
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