CVE-2026-96589

Gitea private repository access retained after rejected transfer

Published Oct 6, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

When a private repository is transferred to a user who does not have prior access, Gitea temporarily grants that recipient read access as a collaborator so the recipient can inspect the repository. If the transfer is later rejected or cancelled, the collaborator status is not revoked, leaving the recipient with persistent read access to all private data including code, issues, pull requests, wiki and the ability to clone the repository. The owner is not notified that access was retained, meaning private information remains exposed after a transfer rejection.

Affected Systems

This vulnerability affects Gitea installations running versions prior to 28.0.0. The 28.0.0 release addresses the issue by removing retained read access from rejected or cancelled transfers while preserving other existing collaborators.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate severity, and the EPSS score of less than 1% suggests a low probability of current exploitation. The vulnerability is exploitably via the normal web interface used to transfer repositories; the likely attack vector is initiating or being the target of a repository transfer request. Although not listed in the CISA KEV catalog, the persistence of granted read access can expose confidential code and project data, and the owner’s lack of notification compounds the risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.0.0 or later to eliminate the flaw
  • If an immediate upgrade is not possible, manually revoke the collaborator role that was granted during the rejected transfer and verify that no unintended collaborators remain
  • Enable logging and monitoring of repository transfer events and collaborator changes to detect any future retention of access

Generated by OpenCVE AI on October 7, 2026 at 18:49 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description 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.
Title Gitea private repository access retained after rejected transfer
Weaknesses CWE-672
CWE-863
References
Weaknesses
  • CWE-672

    Operation on a Resource after Expiration or Release

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Oct 7, 2026, 2:30 PM
Reserved
Oct 4, 2026, 9:59 PM
Status
Analyzed
Published
Oct 6, 2026, 8:17 PM
Modified
Oct 13, 2026, 3:36 PM