Bug 2547068 (CVE-2026-96589)

Summary: CVE-2026-96589 code.gitea.io/gitea: Gitea: Unauthorized read access to private repositories via cancelled repository transfer
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerability-draftAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: gbenhaim, niyer, twaugh
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Gitea. When a private repository ownership transfer is initiated to a user who lacks access, Gitea temporarily grants that recipient collaborator read access to review the repository. If the transfer is subsequently cancelled or rejected, the system fails to revoke these permissions. This flaw allows the recipient to retain persistent, unauthorized read access to the private repository, enabling them to clone the source code and view issues, pull requests, and wiki documentation without the repository owner's knowledge.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-10-06 19:43:44 UTC
When a private repository is transferred to a user who lacks access, Gitea grants that recipient temporary read access as a collaborator so they can review the repository. Rejecting or cancelling the transfer did not revoke this collaboration, so the named recipient kept persistent read access to the private repository, including its code, issues, pull requests and wiki, and could clone it. The repository owner was not notified. Transfer-granted access is now removed while collaborations that existed before the transfer are preserved.