← Back
CVE-2026-52805
high
CVSS 8.7
SSRF (Server-Side Request Forgery) in gogs.io/gogs (CVE-2026-52805)
Summary
SSRF in gogs.io/gogs (CVE-2026-52805). Confidential information can be exposed externally. Mitigation: upgrade to `0.14.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-52805** has been found in gogs.io/gogs.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade gogs.io/gogs to **0.14.3** or later.
If unsure, ask your IT team or search "gogs.io/gogs CVE-2026-52805" on the vendor's site.
CVE-2026-52805 (gogs.io/gogs) — CWE-918 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Patched: `0.14.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 gogs.io/gogs.
📍 Affected scope
gogs.io/gogs — .
🔥 Severity
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.14.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 'gogs.io/gogs' .` 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 'gogs.io/gogs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `gogs.io/gogs` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade gogs.io/gogs to 0.14.3ステージング環境で 0.14.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
gogs.io/gogs
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.14.3"}]}]