← Back
CVE-2026-27783
medium
CVSS 4.3
Vulnerability in code.gitea.io/gitea (CVE-2026-27783)
Summary
vulnerability in code.gitea.io/gitea (CVE-2026-27783). Risk of unauthorized operations or information disclosure. Exploitable via `GET /repos/{owner}/{repo}/issue_templates`. Mitigation: upgrade to `1.26.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-27783** has been found in code.gitea.io/gitea.
Attackers can target a specific entry point like `GET /repos/{owner}/{repo}/issue_templates` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade code.gitea.io/gitea to **1.26.2** or later.
If unsure, ask your IT team or search "code.gitea.io/gitea CVE-2026-27783" on the vendor's site.
CVE-2026-27783 (code.gitea.io/gitea) — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /repos/{owner}/{repo}/issue_templates / GET /repos/{owner}/{repo}/issue_config / GET /repos/{owner}/{repo}/issue_config/validate / GET /api/v1/repos/victim-org/private-repo/issue_templates
Patched: `1.26.2` — apply immediately
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.
❓ What is the problem
**A vulnerability** (CWE-862) exists in code.gitea.io/gitea. Attackers reach the vulnerable code path via `GET /repos/{owner}/{repo}/issue_templates` without authentication.
📍 Affected scope
code.gitea.io/gitea — . Attack surface: GET /repos/{owner}/{repo}/issue_templates / GET /repos/{owner}/{repo}/issue_config / GET /repos/{owner}/{repo}/issue_config/validate / GET /api/v1/repos/victim-org/private-repo/issue_templates.
🔥 Severity
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.26.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `GET /repos/{owner}/{repo}/issue_templates` requests with malformed payloads or SQL meta-characters. Run `grep -r 'code.gitea.io/gitea' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'code.gitea.io/gitea' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `code.gitea.io/gitea` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /repos/{owner}/{repo}/issue_templates' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /repos/{owner}/{repo}/issue_templates` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade code.gitea.io/gitea to 1.26.2ステージング環境で 1.26.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /repos/{owner}/{repo}/issue_templates on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
code.gitea.io/gitea
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.2"}]}]