Answer in brief
CVE-2026-59765 records a High severity (CVSS 8.3) vulnerability in Gitea prior to 1.27.0 SSRF via Migration URI Fetch Bypass. The current sources do not mark it as known exploited. The current feed maps Gitea/Gitea (generic), Gitea/Gitea (generic), Gitea/Gitea Open Source Git Server (generic), Gitea/Gitea Open Source Git Server (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Gitea/Gitea (generic), Gitea/Gitea (generic), Gitea/Gitea Open Source Git Server (generic), Gitea/Gitea Open Source Git Server (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Gitea/Giteageneric | >=0 <=1.26.4 | Not reported |
| Gitea/Giteageneric | 0 | Not reported |
| Gitea/Gitea Open Source Git Servergeneric | 0 | Not reported |
| Gitea/Gitea Open Source Git Servergeneric | >=0 <=1.26.4 | Not reported |
| code.gitea.io/giteago | >=0 <1.27.0 | 1.27.0 |
| code.gitea.io/giteago | <1.27.0 | 1.27.0 |
| gitea.devgo | >=0 <1.27.0 | 1.27.0 |
| gitea.devgo | <1.27.0 | 1.27.0 |
Published upstream
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 13, 2026
Gitea prior to 1.27.0 contains a server-side request forgery vulnerability that allows authenticated attackers to bypass SSRF protections by exploiting HTTP fetch operations in migration and OAuth avatar code paths that use Go's default http.Get without a custom DialContext. Attackers can supply arbitrary URLs through release asset download URLs, pull-request patch URLs, or OAuth avatar endpoints to reach internal services, cloud instance-metadata endpoints, or read local files such as the application configuration containing database credentials and signing secrets, with exfiltrated content persisted as migration release assets for later retrieval.
Quoted source text, attributed separately from HOL analysis.