Gitea · Gitea · published 2026-10-06
CVE-2026-101027Gitea migration SSRF through ALLOWED_DOMAINS address check bypass
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-101027 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 14% of all CVEs. This Gitea vulnerability: CVSS 7.7 (v3.1). Fixed upstream in Gitea 28.1.0, 28.0.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 28.1.0, 28.0.0.
Patch events
DevOpsGitea
Gitea security releases: 28.1.0, 28.0.0
Upgrade to
28.1.028.0.0Why: CVE-2026-89182: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (14th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.7 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Gitea Gitea
0through1.27.3(affected)
Description (from the CVE record)#
When `[migrations] ALLOWED_DOMAINS` was configured, a hostname matching the allow list was accepted without checking its resolved address against the local-network restrictions. A user who can start repository migrations and control the DNS of an allowed hostname could make it resolve to loopback or private addresses and bypass `ALLOW_LOCALNETWORKS = false`, reaching internal services from the Gitea server. Instances without `ALLOWED_DOMAINS` configured are not affected by this specific bypass.
Quoted from the CVE Program record.