Cross-Site Scripting (XSS) in gogs.io/gogs (CVE-2026-52798)
Summary
Cross-site scripting in gogs.io/gogs (CVE-2026-52798). Confidential information can be exposed externally. Exploitable via poc. 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, although .ipynb previews are sanitized on the server side via /-/api/sanitize_ipynb, the inserted content is re-rendered on the client side without sanitization using marked() on elements with the .nb-markdown-cell class. During this process, links containing schemes such as javascript: can be regenerated. As a result, when a victim views an attacker-crafted .ipynb file and clicks the link, arbitrary JavaScript is executed in the Gogs origin, leading to a click-based Stored XSS. 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-52798 has been found in gogs.io/gogs.
Attackers can target a specific entry point like poc over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.9/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-52798" on the vendor's site.
CVE-2026-52798 (gogs.io/gogs) — CWE-79 / CVSS v3 8.9
Attack vector: remote (network-reachable)
Attack surface: poc
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.
Cross-site scripting (XSS) (CWE-79) exists in gogs.io/gogs. Attackers reach the vulnerable code path via poc.
Check the vendor advisory for the affected versions of gogs.io/gogs. Attack surface: poc.
Severity: High (CVSS 8.9/10). Confidential information can be exposed externally.
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 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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gogs.io/gogs to 0.14.3ステージング環境で 0.14.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
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