Quick answers
- Is CVE-2026-52805 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52805 being exploited in the wild.
- How severe is CVE-2026-52805?
- High severity, with a CVSS score of 8.7, published 24 June 2026.
- Which products and versions are affected?
- gogs.io/gogs (Go) < 0.14.3, SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.14.3; Gogs < 0.14.3.
- Is there a fix for CVE-2026-52805?
- Yes. gogs.io/gogs (Go): upgrade to 0.14.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-52805 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-52805?
- Check whether you run gogs.io/gogs (Go) or Gogs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- gogs.io/gogs (Go): upgrade to 0.14.3 or later
go get gogs.io/gogs@v0.14.3
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in Gogs' repository migration and mirror synchronization logic. While Gogs validates the initial URL hostname against a blocklist, the underlying 'git clone --mirror' command follows HTTP redirects without re-validating the new destination. Additionally, the recurring mirror sync failed to re-validate hostnames, allowing an attacker to bypass initial checks via DNS rebinding or by changing a benign URL to redirect to an internal endpoint (e.g., 127.0.0.1) after the mirror was established. This allows an authenticated attacker to import contents from internal-only services into an attacker-controlled repository. The fix in version 0.14.3 disables HTTP redirects for git operations and implements mandatory hostname re-validation before every sync.
Affected products
- Gogs Gogs < 0.14.3
Identifiers
- CVE-2026-52805
- GHSA-g2f5-gjr4-qjvm
- GO-2026-5387
Timeline
- 2026-06-05: patched: Fix committed to main branch.
- 2026-06-07: advisory: Release v0.14.3 published.
- 2026-06-24: disclosed: CVE-2026-52805 published.