Authorization Flaw in gitea.dev (CVE-2026-58431)
Summary
Vulnerability in gitea.dev (CVE-2026-58431). Risk of unauthorized operations or information disclosure. Exploitable via ctx.Org.Team. Mitigation: upgrade to 1.27.0 or later.
Original description
The description as published by the source.
Public-only API token restriction is not enforced on team API routes
Source: GitHub Security Advisories (Global) 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-58431 has been found in gitea.dev.
Attackers can target a specific entry point like ctx.Org.Team over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/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-58431" on the vendor's site.
CVE-2026-58431 (gitea.dev) — CWE-863 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ctx.Org.Team / ctx.Org.Organization / checkTokenPublicOnly
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.
Incorrect authorization (CWE-863) exists in gitea.dev. Attackers reach the vulnerable code path via ctx.Org.Team.
Check the vendor advisory for the affected versions of gitea.dev. Attack surface: ctx.Org.Team / ctx.Org.Organization / checkTokenPublicOnly.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.27.0.
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.dev' . 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.dev' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gitea.devを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gitea.dev to 1.27.0ステージング環境で 1.27.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory blog.gitea.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com