← Back
CVE-2026-28740
high
CVSS 7.1
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-639) exists in gitea.dev. Attackers reach the vulnerable code path via ``unit.TypeInvalid`` without authentication.
📍 Affected scope
gitea.dev — . Attack surface: `unit.TypeInvalid` / `team_repo` / `team_user` / `team_unit`.
🔥 Severity
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.26.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade gitea.dev to 1.26.3ステージング環境で 1.26.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
gitea.dev
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.3"}]}]
References
- web 88ee5874-cf24-4952-aea0-31affedb7ff2
- web https://github.com/go-gitea/gitea/pull/38050
- web https://github.com/go-gitea/gitea/releases/tag/v1.26.3
- web https://github.com/go-gitea/gitea/security/advisories/GHSA-2m9v-5q2g-58vq
- web https://nvd.nist.gov/vuln/detail/CVE-2026-28740
- web https://github.com/go-gitea/gitea/commit/1c7b7ea72df7cf81e88b8e09049608254d32e56e
- web https://github.com/go-gitea/gitea/commit/7b4a1a1a118501b9d0260301dfed7f52dfc36ee9
- web https://blog.gitea.com/release-of-1.26.3-and-1.26.4
- web https://github.com/advisories/GHSA-2m9v-5q2g-58vq