Most recent entries from all

EUVD-2026-330400

fkie_cve-2026-52796

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.

GHSA-4j89-2c4f-44c6 — Gogs has DoS in rendering issue index pattern

Affected: Go: gogs.io/gogs

### Summary Special template of issue index pattern may cause panic.

### Details

in internal/markup/markup.go

```go link = fmt.Sprintf(`<a href="%s">%s</a>`, com.Expand(metas["format"], metas), m) ```

Issue index pattern is rendered to link with `com.Expand`.

However, `com.Expand` is not safe.

```go i = strings.Index(template, "}") if s, ok := match[template[:i]]; ok { ```

when `{` is found but `}` not found, i comes to 1, template[:-1] will be called, and then panicked

![image](https://user-images.githubusercontent.com/38121125/285883766-64873c44-d325-44ce-96a8-badbaadab178.png)

finally, all pages than contains issue index are unavailable.

### PoC

1. set issue index pattern as follow

![image](https://user-images.githubusercontent.com/38121125/285878157-c5fe848e-0fbd-4fdb-92d4-5eb01df2b8ca.png)

2. add a commit which point to an issue in its msg

![image](https://user-images.githubusercontent.com/38121125/285879545-bc360503-49b9-453f-aa24-9a5c5a45cf10.png)

using `#1` above

### Impact

DoS that cause part of pages of the specify repo unavailable.

WID-SEC-W-2026-2013 — Gogs: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Gogs ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen – sogar mit erweiterten Berechtigungen, was zur vollständigen Kontrolle über das System führen kann –, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen, Benutzer auf bösartige Websites umzuleiten oder einen Denial-of-Service-Zustand zu verursachen.