Authorization Flaw in code.gitea.io/gitea (CVE-2026-58443)
Summary
Vulnerability in code.gitea.io/gitea (CVE-2026-58443). Data can be tampered with by attackers. Exploitable via POST /api/v1/repos/{public-owner}/{public-repo}/pulls/{index}/update. Mitigation: upgrade to 1.27.0 or later.
Original description
The description as published by the source.
Public-only repository tokens can update private PR head branches
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-58443 has been found in code.gitea.io/gitea.
Attackers can target a specific entry point like POST /api/v1/repos/{public-owner}/{public-repo}/pulls/{index}/update over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 9.1/10.
What to do: upgrade code.gitea.io/gitea to 1.27.0 or later.
If unsure, ask your IT team or search "code.gitea.io/gitea CVE-2026-58443" on the vendor's site.
CVE-2026-58443 (code.gitea.io/gitea) — CWE-863 / CVSS v3 9.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/repos/{public-owner}/{public-repo}/pulls/{index}/update / ctx.Repo.Repository / pull.HeadRepo / push
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 code.gitea.io/gitea. Attackers reach the vulnerable code path via POST /api/v1/repos/{public-owner}/{public-repo}/pulls/{index}/update.
Check the vendor advisory for the affected versions of code.gitea.io/gitea. Attack surface: POST /api/v1/repos/{public-owner}/{public-repo}/pulls/{index}/update / ctx.Repo.Repository / pull.HeadRepo / push.
Severity: Critical (CVSS 9.1/10). Data can be tampered with by attackers.
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 POST /api/v1/repos/{public-owner}/{public-repo}/pulls/{index}/update 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 'POST /api/v1/repos/{public-owner}/{public-repo}/pulls/{index}/update' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/repos/{public-owner}/{public-repo}/pulls/{index}/updateへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade code.gitea.io/gitea to 1.27.0ステージング環境で 1.27.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v1/repos/{public-owner}/{public-repo}/pulls/{index}/update 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