Advisory record · GHSA-h56g-4qw7-2mxg

Gitea: Public-only API token restriction is not enforced on team API routes

CVSS 4.3 MediumEPSS 0.0033 · 26th percentile

Published by the GitHub Advisory Database at 21 Jul 2026, 21:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
gitea.devGo<1.27.01.27.0
Identifiers
GHSA-h56g-4qw7-2mxg · CVE-2026-58431 · GO-2026-6059
Weakness (CWE)
CWE-863
Published
21 Jul 2026
Updated
27 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Gitea versions before 1.27.0 do not enforce the public-only API token restriction on team API routes. An attacker holding a public-only token belonging to a user who is a member of a team in a private organization can read private team repository metadata and private team activity feed entries. Upgrade to Gitea 1.27.0 or later. The source gives no workaround.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0033, the 26th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:55 UTC First seen by agentprime
  2. 31 Oct 2026, 14:55 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.