Lucene search
+L

24 matches found

SUSE CVE
SUSE CVE
•added 2026/08/11 12:10 a.m.•18 views

SUSE CVE-2026-24451

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...

7.5CVSS6.1AI score0.00449EPSS
SaveExploits0References2
osv_go
osv_go
•added 2026/07/27 3:32 p.m.•34 views

GO-2026-6081 Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private in code.gitea.io/gitea

Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private in code.gitea.io/gitea...

7.5CVSS6.1AI score0.00449EPSS
SaveExploits0References5
Positive Technologies
Positive Technologies
•added 2026/07/27 12:00 a.m.•25 views

PT-2026-65378

Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private in code.gitea.io/gitea...

7.5CVSS6.2AI score0.00449EPSS
SaveExploits0References6
Github Security Blog
Github Security Blog
•added 2026/07/21 9:42 p.m.•32 views

Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private

Summary The POST /api/v1/repos/owner/repo/merge-upstream endpoint continues to synchronize commits from a parent repository after the parent repository has been changed from public to private. A fork created while the parent repository was public can still receive commits made after the parent...

7.5CVSS6AI score0.00449EPSS
SaveExploits0References6Affected Software1
EUVD
EUVD
•added 2026/07/21 9:42 p.m.•36 views

EUVD-2026-41619

Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private...

7.5CVSS6.1AI score0.00449EPSS
SaveExploits0References5
osv_ghsa
osv_ghsa
•added 2026/07/21 9:42 p.m.•28 views

GHSA-WRF9-R3H7-7X5V Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private

Summary The POST /api/v1/repos/owner/repo/merge-upstream endpoint continues to synchronize commits from a parent repository after the parent repository has been changed from public to private. A fork created while the parent repository was public can still receive commits made after the parent...

7.5CVSS6AI score0.00449EPSS
SaveExploits0References6
Snyk
Snyk
•added 2026/07/03 10:19 p.m.•15 views

Information Exposure

Overview Affected versions of this package are vulnerable to Information Exposure via the fork synchronization process. An attacker can access private repository data by continuing to synchronize a fork after the parent repository's visibility changes from public to private. Remediation Upgrade...

7.5CVSS6AI score0.00449EPSS
SaveExploits0References2
Snyk
Snyk
•added 2026/07/03 10:19 p.m.•17 views

Information Exposure

Overview Affected versions of this package are vulnerable to Information Exposure via the fork synchronization process. An attacker can access private repository data by continuing to synchronize a fork after the parent repository's visibility changes from public to private. Remediation Upgrade...

7.5CVSS6AI score0.00449EPSS
SaveExploits0References2
Snyk
Snyk
•added 2026/07/03 10:19 p.m.•22 views

Information Exposure

Overview Affected versions of this package are vulnerable to Information Exposure via the fork synchronization process. An attacker can access private repository data by continuing to synchronize a fork after the parent repository's visibility changes from public to private. Remediation Upgrade...

7.5CVSS6AI score0.00449EPSS
SaveExploits0References2
Snyk
Snyk
•added 2026/07/03 10:19 p.m.•24 views

Information Exposure

Overview Affected versions of this package are vulnerable to Information Exposure via the fork synchronization process. An attacker can access private repository data by continuing to synchronize a fork after the parent repository's visibility changes from public to private. Remediation Upgrade...

7.5CVSS6AI score0.00449EPSS
SaveExploits0References2
Snyk
Snyk
•added 2026/07/03 10:19 p.m.•14 views

Information Exposure

Overview Affected versions of this package are vulnerable to Information Exposure via the fork synchronization process. An attacker can access private repository data by continuing to synchronize a fork after the parent repository's visibility changes from public to private. Remediation Upgrade...

7.5CVSS6AI score0.00449EPSS
SaveExploits0References2
Snyk
Snyk
•added 2026/07/03 10:19 p.m.•21 views

Information Exposure

Overview Affected versions of this package are vulnerable to Information Exposure via the fork synchronization process. An attacker can access private repository data by continuing to synchronize a fork after the parent repository's visibility changes from public to private. Remediation Upgrade...

7.5CVSS6AI score0.00449EPSS
SaveExploits0References2
Snyk
Snyk
•added 2026/07/03 10:19 p.m.•20 views

Information Exposure

Overview Affected versions of this package are vulnerable to Information Exposure via the fork synchronization process. An attacker can access private repository data by continuing to synchronize a fork after the parent repository's visibility changes from public to private. Remediation Upgrade...

7.5CVSS6AI score0.00449EPSS
SaveExploits0References2
Snyk
Snyk
•added 2026/07/03 10:19 p.m.•21 views

Information Exposure

Overview Affected versions of this package are vulnerable to Information Exposure via the fork synchronization process. An attacker can access private repository data by continuing to synchronize a fork after the parent repository's visibility changes from public to private. Remediation Upgrade...

7.5CVSS6AI score0.00449EPSS
SaveExploits0References2
NVD
NVD
•added 2026/07/03 9:16 p.m.•34 views

CVE-2026-24451

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...

7.5CVSS0.00449EPSS
SaveExploits0References4
Mend
Mend
•added 2026/07/03 8:19 p.m.•13 views

CVE-2026-24451

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...

8.7CVSS6.1AI score0.00449EPSS
SaveExploits0References8
osv_cve
osv_cve
•added 2026/07/03 8:19 p.m.•26 views

CVE-2026-24451 Gitea fork synchronization can expose private parent repository data

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...

7.5CVSS6.1AI score0.00449EPSS
SaveExploits0References6
CVE
CVE
•added 2026/07/03 8:19 p.m.•107 views

CVE-2026-24451

The Gitea version 1.26.2 repository management system contains a vulnerability in the POST /api/v1/repos/{owner}/{repo}/merge-upstream endpoint. The root cause is a lack of protection for service data, where the synchronization endpoint continues to import new commits from a parent repository eve...

7.5CVSS6.1AI score0.00449EPSS
SaveExploits0References4
Cvelist
Cvelist
•added 2026/07/03 8:19 p.m.•79 views

CVE-2026-24451 Gitea fork synchronization can expose private parent repository data

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...

0.00449EPSS
SaveExploits0References4
attackerkb
attackerkb
•added 2026/07/03 8:19 p.m.•23 views

CVE-2026-24451

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...

6.2AI score0.00449EPSS
SaveExploits0References5Affected Software1
Rows per page
Query Builder