← Back
CVE-2026-58416
high
CVSS 7.1
Vulnerability in gitea.dev (CVE-2026-58416)
Summary
vulnerability in gitea.dev (CVE-2026-58416). Confidential information can be exposed externally. Exploitable via `GET /userb/repoB.git/info/refs`. Mitigation: upgrade to `1.27.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-58416** has been found in gitea.dev.
Attackers can target a specific entry point like `GET /userb/repoB.git/info/refs` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade gitea.dev to **1.27.0** or later.
If unsure, ask your IT team or search "gitea.dev CVE-2026-58416" on the vendor's site.
CVE-2026-58416 (gitea.dev) — CWE-280 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /userb/repoB.git/info/refs / `GetActionsUserRepoPermission` / `taskRepo` / `repo`
Patched: `1.27.0` — 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-280) exists in gitea.dev. Attackers reach the vulnerable code path via `GET /userb/repoB.git/info/refs` without authentication.
📍 Affected scope
gitea.dev — . Attack surface: GET /userb/repoB.git/info/refs / `GetActionsUserRepoPermission` / `taskRepo` / `repo`.
🔥 Severity
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.27.0**.
🛡️ 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 /userb/repoB.git/info/refs` requests with malformed payloads or SQL meta-characters. Run `grep -r 'gitea.dev' .` 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 'gitea.dev' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `gitea.dev` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /userb/repoB.git/info/refs' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /userb/repoB.git/info/refs` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade gitea.dev to 1.27.0ステージング環境で 1.27.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /userb/repoB.git/info/refs on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
gitea.dev
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.27.0"}]}]
References
- web 88ee5874-cf24-4952-aea0-31affedb7ff2
- web https://github.com/go-gitea/gitea/pull/38214
- web https://github.com/go-gitea/gitea/commit/1d43b736b5a16c5f80cfdcd9a9448a9c983ddaa0
- web 88ee5874-cf24-4952-aea0-31affedb7ff2
- web https://github.com/advisories/GHSA-fj8v-hjwv-qm88
- web 88ee5874-cf24-4952-aea0-31affedb7ff2