Authorization Flaw in Gitea (CVE-2026-97208)
Summary
Vulnerability in Gitea (CVE-2026-97208). Data can be tampered with by attackers. Exploitable via POST /api/v1/repos/{owner}/{repo}/push_mirrors.
Original description
The description as published by the source.
The Gitea API endpoint for creating push mirrors (POST /api/v1/repos/{owner}/{repo}/push_mirrors) checked only whether mirroring was enabled and not the [mirror] DISABLE_NEW_PUSH setting that the web interface enforces. A repository administrator could therefore create new push mirrors on instances where the site administrator had disabled them. A push mirror pushes all refs of the repository to a remote chosen by the caller, on each commit or on a schedule.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-97208 has been found in Gitea.
Attackers can target a specific entry point like POST /api/v1/repos/{owner}/{repo}/push_mirrors over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 4.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Gitea CVE-2026-97208" on the vendor's site.
CVE-2026-97208 (Gitea) — CWE-863 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/repos/{owner}/{repo}/push_mirrors
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.
Incorrect authorization (CWE-863) exists in Gitea. Attackers reach the vulnerable code path via POST /api/v1/repos/{owner}/{repo}/push_mirrors.
Check the vendor advisory for the affected versions of Gitea. Attack surface: POST /api/v1/repos/{owner}/{repo}/push_mirrors.
Severity: Medium (CVSS 4.9/10). Data can be tampered with by attackers.
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 POST /api/v1/repos/{owner}/{repo}/push_mirrors requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/v1/repos/{owner}/{repo}/push_mirrors' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/repos/{owner}/{repo}/push_mirrorsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/v1/repos/{owner}/{repo}/push_mirrors on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- patch github.com
- patch github.com
- web blog.gitea.com
- web github.com
- web nvd.nist.gov