Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-22874 critical CVSS 9.6

SSRF (Server-Side Request Forgery) in code.gitea.io/gitea (CVE-2026-22874)

Summary

SSRF in code.gitea.io/gitea (CVE-2026-22874). Confidential information can be exposed externally. Exploitable via ``MatchBuiltinExternal``. Mitigation: upgrade to `1.26.3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-22874** has been found in code.gitea.io/gitea. Attackers can target a specific entry point like ``MatchBuiltinExternal`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: 9.6/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-22874" on the vendor's site.
CVE-2026-22874 (code.gitea.io/gitea) — CWE-918 / CVSS v3 9.6 Attack vector: remote (network-reachable) / no user interaction Attack surface: `MatchBuiltinExternal` / `HostMatchList.checkIP` / `gitea_ssrf_test.patch` / `TestSSRFBypassRanges` 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
**SSRF** (CWE-918) exists in code.gitea.io/gitea. Attackers reach the vulnerable code path via ``MatchBuiltinExternal`` without authentication.
📍 Affected scope
code.gitea.io/gitea — . Attack surface: `MatchBuiltinExternal` / `HostMatchList.checkIP` / `gitea_ssrf_test.patch` / `TestSSRFBypassRanges`.
🔥 Severity
Severity: Critical (CVSS 9.6/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 '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. 6
    Apply patch patch 
    Upgrade code.gitea.io/gitea to 1.26.3

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

  3. 7
    Post-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.3"}]}]

References

🍪 About cookies

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

Details →