CVE-2026-20800: GO-2026-4362 - Gitea improperly exposes issue and pull request titles in code.gitea.io/gitea

CVE-2026-20800 · Severity: medium · CVSS 4 · Published 2026-02-02

Gitea improperly exposes issue and pull request titles in code.gitea.io/gitea

Technologies: code.gitea.io/gitea (Go), github.com/go-gitea/gitea (Go). Vendors: Go.

Quick answers

Is CVE-2026-20800 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-20800 being exploited in the wild.
How severe is CVE-2026-20800?
Medium severity, with a CVSS score of 4, published 2 February 2026.
Which products and versions are affected?
code.gitea.io/gitea (Go) SEMVER:introduced=0,fixed=1.25.4; github.com/go-gitea/gitea (Go) SEMVER:introduced=0,fixed=1.25.4.
Is there a fix for CVE-2026-20800?
Yes. code.gitea.io/gitea (Go): upgrade to 1.25.4 or later; github.com/go-gitea/gitea (Go): upgrade to 1.25.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-20800?
Check whether you run code.gitea.io/gitea (Go) or github.com/go-gitea/gitea (Go) 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

  • code.gitea.io/gitea (Go): upgrade to 1.25.4 or later
    go get code.gitea.io/gitea@v1.25.4
  • github.com/go-gitea/gitea (Go): upgrade to 1.25.4 or later
    go get github.com/go-gitea/gitea@v1.25.4

Affected products

  • code.gitea.io/gitea (Go) SEMVER:introduced=0,fixed=1.25.4
  • github.com/go-gitea/gitea (Go) SEMVER:introduced=0,fixed=1.25.4

Identifiers

  • CVE-2026-20800
  • GHSA-2vgv-hgv4-22mh
  • GO-2026-4362

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.