← Back
CVE-2026-28744
high
CVSS 8.1
Authorization Flaw in code.gitea.io/gitea (CVE-2026-28744)
Summary
vulnerability in code.gitea.io/gitea (CVE-2026-28744). Confidential information can be exposed externally. Exploitable via ``ctx.IsBasicAuth``. Mitigation: upgrade to `1.26.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-28744** has been found in code.gitea.io/gitea.
Attackers can target a specific entry point like ``ctx.IsBasicAuth`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/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-28744" on the vendor's site.
CVE-2026-28744 (code.gitea.io/gitea) — CWE-863 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `ctx.IsBasicAuth` / `ApiTokenScope` / `user2`
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.
❓ What is the problem
**incorrect authorization** (CWE-863) exists in code.gitea.io/gitea. Attackers reach the vulnerable code path via ``ctx.IsBasicAuth`` without authentication.
📍 Affected scope
code.gitea.io/gitea — . Attack surface: `ctx.IsBasicAuth` / `ApiTokenScope` / `user2`.
🔥 Severity
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.26.2**.
🛡️ 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 'code.gitea.io/gitea' .` 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 'code.gitea.io/gitea' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `code.gitea.io/gitea` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade code.gitea.io/gitea to 1.26.2ステージング環境で 1.26.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
code.gitea.io/gitea
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.2"}]}]