Vulnerability in Gitea (CVE-2026-105267)
Summary
Vulnerability in Gitea (CVE-2026-105267). Data can be tampered with by attackers. Exploitable via POST /{owner}/{repo}/tags/delete.
Original description
The description as published by the source.
The Gitea web route for deleting tags (POST /{owner}/{repo}/tags/delete) requires only write access to the Code unit, but shares its handler with release deletion and did not check that the target was a plain tag. A collaborator with Code write access and without Releases write access could permanently delete published releases of that repository, including their attachments. Protected tag rules covering the release tag still blocked the deletion.
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-105267 has been found in Gitea.
Attackers can target a specific entry point like POST /{owner}/{repo}/tags/delete over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Gitea CVE-2026-105267" on the vendor's site.
CVE-2026-105267 (Gitea) — CWE-732 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /{owner}/{repo}/tags/delete
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-732) exists in Gitea. Attackers reach the vulnerable code path via POST /{owner}/{repo}/tags/delete.
Check the vendor advisory for the affected versions of Gitea. Attack surface: POST /{owner}/{repo}/tags/delete.
Severity: High (CVSS 8.1/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 /{owner}/{repo}/tags/delete 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 /{owner}/{repo}/tags/delete' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /{owner}/{repo}/tags/deleteへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /{owner}/{repo}/tags/delete on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- patch github.com
- patch github.com
- patch github.com
- web blog.gitea.com
- web github.com