PT-2026-63291 · Gitea+1 · Gitea+1

·

CVE-2026-58416

·

Published

2026-07-21

·

Updated

2026-08-26

CVSS v3.1

7.1

High

VectorAV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N
Name of the Vulnerable Software and Affected Versions Gitea version 1.26.2
Description A confidentiality breach exists where an attacker-controlled fork pull-request workflow can gain read access to a third private repository. This occurs because the GetActionsUserRepoPermission() function in models/perm/access/repo permission.go fails to implement a fork pull-request guard in the collaborative-owner logic branch. While other access paths correctly deny access to fork pull-requests, this specific branch allows a task token to obtain maxPerm (code-read) if the target repository B trusts the owner of the base repository A as a collaborative owner, provided that repository A is private.
Technical details include:
  • API Endpoints: /userb/repoB.git/info/refs?service=git-upload-pack (used during git-HTTP cloning).
  • Vulnerable Parameters or Variables: task.IsForkPullRequest is not checked in the collaborative-owner branch.
  • Function Names: GetActionsUserRepoPermission()
Recommendations Update Gitea to a version where the GetActionsUserRepoPermission() function is patched to include the !task.IsForkPullRequest guard within the collaborative-owner check to ensure fork pull-requests are denied cross-repo access.

Exploit

Fix

DoS

Incorrect Authorization

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-58416
GHSA-FJ8V-HJWV-QM88
GO-2026-6052
OPENSUSE-SU-2026:21483-1

Affected Products

Gitea
Red Os