Server-side Request Forgery (SSRF) Affecting github.com/go-gitea/gitea/services/repository package, versions <1.27.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-GITHUBCOMGOGITEAGITEASERVICESREPOSITORY-18752781
- published13 Aug 2026
- disclosed21 Jul 2026
- creditcyberlanc3r
Introduced: 21 Jul 2026
CVE-2026-57894 Â (opens in a new tab)How to fix?
Upgrade github.com/go-gitea/gitea/services/repository to version 1.27.0 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the repository migration and mirror synchronization process. An attacker can access internal Git repositories and exfiltrate sensitive data by submitting a crafted migration URL that causes the server to follow an HTTP redirect to an otherwise restricted internal endpoint.
Note: This is only exploitable if repository migrations are enabled and the attacker has a low-privileged account or self-registration is permitted, and the server can reach internal Git HTTP(S) services that are not directly accessible to the attacker.
Workaround
This vulnerability can be mitigated by disabling Git HTTP redirects for migration clone and mirror fetch operations, or by enforcing strict egress controls to prevent the server from accessing internal resources.