Vulnerability in Gitea (CVE-2026-101027)
Summary
Vulnerability in Gitea (CVE-2026-101027). Confidential information can be exposed externally. Exploitable via ALLOWED_DOMAINS.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-101027 has been found in Gitea.
Attackers can target a specific entry point like ALLOWED_DOMAINS over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Gitea CVE-2026-101027" on the vendor's site.
CVE-2026-101027 (Gitea) — CWE-346 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ALLOWED_DOMAINS
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-346) exists in Gitea. Attackers reach the vulnerable code path via ALLOWED_DOMAINS.
Check the vendor advisory for the affected versions of Gitea. Attack surface: ALLOWED_DOMAINS.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Gitea' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Gitea' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Giteaを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch github.com
- patch github.com
- web blog.gitea.com
- web github.com