Gogs is an open source self-hosted Git service. Prior to 0.14.3, specially crafted issue index pattern can cause a panic when rendering, resulting in denial of service. In internal/markup/markup.go, RenderIssueIndexPattern renders the issue index pattern to a link using com.Expand, which is not safe: when the configured pattern contains an opening brace { but no closing brace }, strings.Index(template, "}") returns -1 and the subsequent slice template[:-1] triggers a panic. Once such a pattern is set, any page in the affected repository that contains an issue index reference such as #1 becomes unavailable. This vulnerability is fixed in 0.14.3.
CVE-2026-52796
This low-severity CVE scores 3.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.5
- EG Score
- 3.5(medium)
- EPSS
- 20.3%
- KEV
- Not listed
Published
June 22, 2026
Last Modified
June 25, 2026
References (2)
- security-advisories@githubhttps://github.com/gogs/gogs/security/advisories/GHSA-4j89-2c4f-44c6
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/gogs/gogs/security/advisories/GHSA-4j89-2c4f-44c6
Vendor Advisories for CVE-2026-52796(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gogs.io/gogs | — | 0.14.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 20× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 21:04 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 02:24 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 07:48 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 13:22 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-25 18:56 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-23 00:30 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-52796?
When was CVE-2026-52796 disclosed?
Is CVE-2026-52796 actively exploited?
What is the CVSS score of CVE-2026-52796?
How do I remediate CVE-2026-52796?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52796
Is Your Infrastructure Affected by CVE-2026-52796?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.