Vulnerability in gitea.dev (CVE-2026-28740)
Summary
Vulnerability in gitea.dev (CVE-2026-28740). Confidential information can be exposed externally. Exploitable via unit.TypeInvalid. Mitigation: upgrade to 1.26.3 or later.
Original description
The description as published by the source.
Gitea versions up to and including 1.26.2 allow Git LFS object reuse to authorize private source objects for users who have repository access but lack Code-unit access.
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-28740 has been found in gitea.dev.
Attackers can target a specific entry point like unit.TypeInvalid over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade gitea.dev to 1.26.3 or later.
If unsure, ask your IT team or search "gitea.dev CVE-2026-28740" on the vendor's site.
CVE-2026-28740 (gitea.dev) — CWE-639 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: unit.TypeInvalid / team_repo / team_user / team_unit
Patched: 1.26.3 — 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.
A vulnerability (CWE-639) exists in gitea.dev. Attackers reach the vulnerable code path via unit.TypeInvalid.
Check the vendor advisory for the affected versions of gitea.dev. Attack surface: unit.TypeInvalid / team_repo / team_user / team_unit.
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.
Update to 1.26.3.
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.26.3ステージング環境で 1.26.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
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 github.com
- web blog.gitea.com
- web github.com