Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-27775 high CVSS 8.8

Authorization Flaw in code.gitea.io/gitea (CVE-2026-27775)

Summary

vulnerability in code.gitea.io/gitea (CVE-2026-27775). Successful exploitation can lead to full system takeover. Exploitable via `POST /{owner}/{repo}.git/git-receive-pack`. Mitigation: upgrade to `1.26.3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-27775** has been found in code.gitea.io/gitea. Attackers can target a specific entry point like `POST /{owner}/{repo}.git/git-receive-pack` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: 8.8/10. What to do: upgrade code.gitea.io/gitea to **1.26.3** or later. If unsure, ask your IT team or search "code.gitea.io/gitea CVE-2026-27775" on the vendor's site.
CVE-2026-27775 (code.gitea.io/gitea) — CWE-863 / CVSS v3 8.8 Attack vector: remote (network-reachable) / no user interaction Attack surface: POST /{owner}/{repo}.git/git-receive-pack / `CanMaintainerWriteToBranch` / `true` / `main` 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
**incorrect authorization** (CWE-863) exists in code.gitea.io/gitea. Attackers reach the vulnerable code path via `POST /{owner}/{repo}.git/git-receive-pack` without authentication.
📍 Affected scope
code.gitea.io/gitea — . Attack surface: POST /{owner}/{repo}.git/git-receive-pack / `CanMaintainerWriteToBranch` / `true` / `main`.
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 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 `POST /{owner}/{repo}.git/git-receive-pack` 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 (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 3
    Hunt for indicators of compromise detect 
    grep 'POST /{owner}/{repo}.git/git-receive-pack' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで `POST /{owner}/{repo}.git/git-receive-pack` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 6
    Apply patch patch 
    Upgrade code.gitea.io/gitea to 1.26.3

    ステージング環境で 1.26.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify 
    Replay attack against POST /{owner}/{repo}.git/git-receive-pack on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go code.gitea.io/gitea
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.3"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →