CVE-2026-58445: Gitea cross-repository label enumeration oracle in DeleteIssueLabel API

CVE-2026-58445 · Severity: low · CVSS 3.1 · Published 2026-07-21

Gitea is an open-source platform for hosting software development projects. A flaw in its API allows an authorized user to determine if specific label IDs exist in other private repositories or organizations they do not have permission to access. While this does not allow the attacker to see the content of the labels or modify any data, it enables them to map out the existence and volume of labels across the entire platform.

Technologies: Gitea, code.gitea.io/gitea (Go), gitea.dev (Go). Vendors: Gitea, Go.

Quick answers

Is CVE-2026-58445 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-58445 being exploited in the wild.
How severe is CVE-2026-58445?
Low severity, with a CVSS score of 3.1, published 21 July 2026.
Which products and versions are affected?
Gitea < 1.27.0; code.gitea.io/gitea (Go) < 1.27.0, SEMVER:introduced=0,fixed=1.27.0; gitea.dev (Go) SEMVER:introduced=0,fixed=1.27.0.
Is there a fix for CVE-2026-58445?
Yes. code.gitea.io/gitea (Go): upgrade to 1.27.0 or later; gitea.dev (Go): upgrade to 1.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-58445 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-58445?
Check whether you run Gitea, code.gitea.io/gitea (Go) or gitea.dev (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.27.0 or later
    go get code.gitea.io/gitea@v1.27.0
  • gitea.dev (Go): upgrade to 1.27.0 or later
    go get gitea.dev@v1.27.0

Technical details

The Gitea API endpoint `DELETE /repos/{owner}/{repo}/issues/{index}/labels/{id}` is vulnerable to an information disclosure oracle. The root cause is that the `DeleteIssueLabel` handler uses a global, unscoped database lookup (`GetLabelByID`) without verifying that the requested label ID belongs to the repository or organization specified in the URL. Because the API returns a 204 status if the ID exists anywhere on the instance and a 422 status if it does not, an authenticated attacker can enumerate the instance-wide label population. Since label IDs are sequential auto-incrementing integers, this allows for cross-tenant existence probing. No cross-repository write occurs because the downstream service only attempts to remove the label from the specific issue in the attacker's own repository. The issue is fixed in version 1.27.0.

Affected products

  • Gitea Gitea < 1.27.0

Identifiers

  • CVE-2026-58445
  • GHSA-pgqf-926r-548m
  • GO-2026-6067

Timeline

  • 2026-07-13: disclosed: Initial report to Gitea
  • 2026-07-21: advisory: GitHub Advisory published

References

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