Lucene search
+L

6 matches found

Kitploit
Kitploit
•added 2026/10/02 12:14 a.m.•11 views

CVE-2017-8759

CVE-2017-8759 Just My ports of CVE-2017-8759 Code shifted to another parent repository. Redirect?...

9.3CVSS7.6AI score0.88698EPSS
SaveExploits14References1
Kitploit
Kitploit
•added 2026/10/02 12:14 a.m.•11 views

CVE-2017-11882

CVE-2017-11882 Empire Port of CVE-2017-11882 Code shifted to another parent repository. Redirect?...

9.3CVSS7.8AI score0.99945EPSS
SaveExploits33References1
OSV
OSV
•added 2026/07/27 3:32 p.m.•11 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.6AI score0.00482EPSS
SaveExploits0References5
Positive Technologies
Positive Technologies
•added 2026/07/27 12:00 a.m.•16 views

PT-2026-65378

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

7.5CVSS6.6AI score0.00482EPSS
SaveExploits0References6
Github Security Blog
Github Security Blog
•added 2026/07/21 9:42 p.m.•18 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.5CVSS6.3AI score0.00482EPSS
SaveExploits0References6Affected Software1
OSV
OSV
•added 2026/07/03 8:19 p.m.•15 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.5CVSS7.2AI score
SaveExploits0References6
Rows per page
Query Builder