Gitea fork synchronization can expose private parent repository data
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Gitea | Gitea Open Source Git Server | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Gitea | Gitea Open Source Git Server |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wrf9-r3h7-7x5v | Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.449% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| 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 |
|