Authorization Flaw in code.gitea.io/gitea (CVE-2026-26231)
Summary
Vulnerability in code.gitea.io/gitea (CVE-2026-26231). Data can be tampered with by attackers. Exploitable via Read. Mitigation: upgrade to 1.26.2 or later.
Original description
The description as published by the source.
Gitea versions up to and including 1.26.1 allow the Allow edits from maintainers permission path to authorize commits to repositories that the user can read but should not be able to write.
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-26231 has been found in code.gitea.io/gitea.
Attackers can target a specific entry point like Read over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.5/10.
What to do: upgrade code.gitea.io/gitea to 1.26.2 or later.
If unsure, ask your IT team or search "code.gitea.io/gitea CVE-2026-26231" on the vendor's site.
CVE-2026-26231 (code.gitea.io/gitea) — CWE-863 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Read / SupportProcReceive / CanMaintainerWriteToBranch / PWNED.txt
Patched: 1.26.2 — 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 Read.
Check the vendor advisory for the affected versions of code.gitea.io/gitea. Attack surface: Read / SupportProcReceive / CanMaintainerWriteToBranch / PWNED.txt.
Severity: High (CVSS 8.5/10). Data can be tampered with by attackers.
Update to 1.26.2.
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 '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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade code.gitea.io/gitea to 1.26.2ステージング環境で 1.26.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory blog.gitea.com
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com