Authorization Flaw in gitea.dev (CVE-2026-58440)
Summary
Vulnerability in gitea.dev (CVE-2026-58440). Confidential information can be exposed externally. Exploitable via GET /api/v1/repos/admin/wh-repo. Mitigation: upgrade to 1.27.0 or later.
Original description
The description as published by the source.
Webhooks created by a collaborator keep firing after their repo access is revoked → ongoing real-time exfiltration of private repo content (incomplete revocation cleanup in DeleteCollaboration)
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-58440 has been found in gitea.dev.
Attackers can target a specific entry point like GET /api/v1/repos/admin/wh-repo over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/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-58440" on the vendor's site.
CVE-2026-58440 (gitea.dev) — CWE-863 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/repos/admin/wh-repo / DeleteCollaboration / issue.body
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 GET /api/v1/repos/admin/wh-repo.
Check the vendor advisory for the affected versions of gitea.dev. Attack surface: GET /api/v1/repos/admin/wh-repo / DeleteCollaboration / issue.body.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
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 GET /api/v1/repos/admin/wh-repo 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
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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/repos/admin/wh-repo' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/repos/admin/wh-repoへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade gitea.dev to 1.27.0ステージング環境で 1.27.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/repos/admin/wh-repo on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
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
- web github.com
- web github.com
- web github.com
- web github.com