Information Disclosure in code.gitea.io/gitea (CVE-2026-58419)
Summary
Vulnerability in code.gitea.io/gitea (CVE-2026-58419). Confidential information can be exposed externally. Exploitable via GET /api/v1/repos/sun/{repo}/issues/1. Mitigation: upgrade to 1.25.4 or later.
Original description
The description as published by the source.
Notification API leaks private issue metadata after access revocation
Source: NIST National Vulnerability Database 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-58419 has been found in code.gitea.io/gitea.
Attackers can target a specific entry point like GET /api/v1/repos/sun/{repo}/issues/1 over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade code.gitea.io/gitea to 1.25.4 or later.
If unsure, ask your IT team or search "code.gitea.io/gitea CVE-2026-58419" on the vendor's site.
CVE-2026-58419 (code.gitea.io/gitea) — CWE-200 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/v1/repos/sun/{repo}/issues/1 / GET /api/v1/notifications / GET /api/v1/notifications/threads/14 / GET /api/v1/notifications/threads/{id}
Patched: 1.25.4 — 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.
Information disclosure (CWE-200) exists in code.gitea.io/gitea. Attackers reach the vulnerable code path via GET /api/v1/repos/sun/{repo}/issues/1 without authentication.
Check the vendor advisory for the affected versions of code.gitea.io/gitea. Attack surface: GET /api/v1/repos/sun/{repo}/issues/1 / GET /api/v1/notifications / GET /api/v1/notifications/threads/14 / GET /api/v1/notifications/threads/{id}.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 1.25.4.
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/sun/{repo}/issues/1 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
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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/repos/sun/{repo}/issues/1' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/repos/sun/{repo}/issues/1への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade code.gitea.io/gitea to 1.25.4ステージング環境で 1.25.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/repos/sun/{repo}/issues/1 on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory blog.gitea.com
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web blog.gitea.com
- web github.com