Privilege Escalation in gogs.io/gogs (CVE-2026-52808)
Summary
Vulnerability in gogs.io/gogs (CVE-2026-52808). Data can be tampered with by attackers. Exploitable via PATCH /api/v1/repos/. Mitigation: upgrade to 0.14.3 or later.
Original description
The description as published by the source.
Gogs is an open source self-hosted Git service. Prior to 0.14.3, three API endpoints — PATCH /api/v1/repos/:owner/:repo/issue-tracker, PATCH /api/v1/repos/:owner/:repo/wiki, and POST /api/v1/repos/:owner/:repo/mirror-sync — are gated by reqRepoWriter() rather than reqRepoAdmin(). The equivalent operations in the web UI sit behind reqRepoAdmin, which requires AccessMode >= AccessModeAdmin. A write-level collaborator (who has AccessMode == AccessModeWrite < AccessModeAdmin) can therefore call these API endpoints directly to disable the native issue tracker or wiki, inject attacker-controlled external tracker/wiki URLs that redirect all repository visitors, or trigger mirror sync — none of which they are authorized to do. This vulnerability is fixed in 0.14.3.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-52808 has been found in gogs.io/gogs.
Attackers can target a specific entry point like PATCH /api/v1/repos/ over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/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-52808" on the vendor's site.
CVE-2026-52808 (gogs.io/gogs) — CWE-269 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /api/v1/repos/ / POST /api/v1/repos/ / PATCH /api/v1/repos/OWNER/REPO/issue-tracker / reqRepoAdmin
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.
A vulnerability (CWE-269) exists in gogs.io/gogs. Attackers reach the vulnerable code path via PATCH /api/v1/repos/.
Check the vendor advisory for the affected versions of gogs.io/gogs. Attack surface: PATCH /api/v1/repos/ / POST /api/v1/repos/ / PATCH /api/v1/repos/OWNER/REPO/issue-tracker / reqRepoAdmin.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 0.14.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PATCH /api/v1/repos/ requests with malformed payloads or SQL meta-characters. Run grep -r 'gogs.io/gogs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PATCH /api/v1/repos/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PATCH /api/v1/repos/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade gogs.io/gogs to 0.14.3ステージング環境で 0.14.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against PATCH /api/v1/repos/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com