CVE-2026-24451

Gitea fork synchronization can expose private parent repository data

Published Jul 3, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-wrf9-r3h7-7x5v Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private
History
Type Values Removed Values Added
Metrics cvssV3_1

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

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea Open Source Git Server
Vendors & Products Gitea
Gitea gitea Open Source Git Server
Type Values Removed Values Added
Description Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.
Title Gitea fork synchronization can expose private parent repository data
Weaknesses CWE-200
CWE-284
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Jul 7, 2026, 5:00 PM
Reserved
Mar 3, 2026, 3:26 AM
Status
Deferred
Published
Jul 3, 2026, 9:16 PM
Modified
Oct 25, 2026, 3:10 PM