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.
Advisories
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wrf9-r3h7-7x5v | Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Tue, 07 Jul 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Mon, 06 Jul 2026 23:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitea
Gitea gitea Open Source Git Server |
|
| Vendors & Products |
Gitea
Gitea gitea Open Source Git Server |
Fri, 03 Jul 2026 20:45:00 +0000
| 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 |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Gitea
Published:
Updated: 2026-07-07T17:00:21.477Z
Reserved: 2026-03-03T03:26:00.298Z
Link: CVE-2026-24451
Updated: 2026-07-07T15:55:06.860Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-07-26T22:30:04Z
Github GHSA