Read the docs
TI-2026-68563 Aliases CVE-2026-101027

Gitea migration SSRF through ALLOWED_DOMAINS address check bypass

Priority LOW 33CWE-346Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-346.

Summary

Gitea through 1.27.3 has a server-side request forgery flaw in repository migrations (CWE-346, Origin Validation Error). When [migrations] ALLOWED_DOMAINS is set, a hostname on the allow list is accepted without checking its resolved address against the local-network restrictions. A user who can start migrations and control the DNS of an allowed hostname can point it at loopback or private addresses, bypass ALLOW_LOCALNETWORKS = false, and reach internal services from the Gitea server. CVSS 3.1 scores this 7.7 HIGH; CISA has not added it to KEV, and the references contain no exploit link.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00233 14th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
GiteaGiteaup to 1.27.3—No fix listedCNA
  • Gitea VendorGitea Affected up to 1.27.3 Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*before 28.0.0VulnerableGitea
  • cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:* Versions before 28.0.0 Vulnerable ·Gitea

Remediation

No fixed version is listed for Gitea through 1.27.3. Instances that do not configure ALLOWED_DOMAINS are not affected by this bypass, so leaving that setting unset avoids it.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-06 Threatist record created from CVE-2026-101027
  2. 2026-10-07 CVSS score added · CISA ADP
  3. 2026-10-07 Weakness changed · CISA ADP
  4. 2026-10-07 CISA SSVC decision points changed

References

  • TI-2026-42785 Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation. KEVCVSS 3.1CRITICAL 9.8
  • TI-2020-11072 The git hook feature in Gitea 1.1.0 through 1.12.5 might allow for authenticated remote… CVSS 3.1HIGH 7.2
  • TI-2022-12910 Gitea before 1.16.7 does not escape git fetch remote. CVSS 3.1HIGH 7.5
  • TI-2019-08404 models/repo_mirror.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 mishandles mirror… CVSS 3.1HIGH 8.8
  • TI-2022-00955 Open Redirect on login in go-gitea/gitea CVSS 3.1MEDIUM 6.1
  • TI-2026-68968 Push-to-create bypass of FORCE_PRIVATE policy in Gitea CVSS 3.1MEDIUM 5.4
See all 80 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences