Quick answers
- Is CVE-2026-52796 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52796 being exploited in the wild.
- How severe is CVE-2026-52796?
- Low severity, with a CVSS score of 3.5, published 24 June 2026.
- Which products and versions are affected?
- gogs.io/gogs (Go) <= 0.14.2, SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.14.3; Gogs < 0.14.3, <= 0.14.2.
- Is there a fix for CVE-2026-52796?
- Yes. gogs.io/gogs (Go): upgrade to 0.14.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-52796 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-52796?
- Check whether you run gogs.io/gogs (Go) or Gogs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- gogs.io/gogs (Go): upgrade to 0.14.3 or later
go get gogs.io/gogs@v0.14.3
Technical details
A denial-of-service vulnerability exists in Gogs due to improper handling of template strings in the issue index pattern rendering logic. In `internal/markup/markup.go`, the `RenderIssueIndexPattern` function utilizes `com.Expand` to process patterns. If a configured pattern contains an opening brace '{' without a corresponding closing brace '}', `strings.Index` returns -1, leading to an out-of-bounds slice operation (`template[:-1]`) that triggers a Go panic. An attacker with repository-level privileges can configure a malicious pattern, causing any page containing an issue reference (e.g., #1) to fail to load. This issue is resolved in version 0.14.3.
Affected products
- Gogs Gogs < 0.14.3
Identifiers
- CVE-2026-52796
- GHSA-4j89-2c4f-44c6
- GO-2026-5124
Timeline
- 2026-06-19: advisory: GitHub Security Advisory published
- 2026-06-24: disclosed: CVE published to NVD