Read the docs
TI-2026-73997 Aliases CVE-2026-59766

Private repository metadata exposed in Gitea after access revocation

Priority LOW 20CWE-284Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA and GitHub. Impact type from CWE-284.

Summary

Gitea from 1.25.4 is affected. The starred-repository and tracked-time API endpoints do not recheck current repository permissions, which is improper access control (CWE-284). A remote user with low privileges whose access to a private repository was revoked can still retrieve repository metadata through /api/v1/user/starred and private issue titles through /api/v1/user/times, if relationships or tracked time were created before the revocation.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

Gitea's starred-repository and tracked-time API endpoints do not re-check current repository permissions before returning data associated with the requesting user. A user whose access to a private repository has been revoked can still retrieve repository metadata through /api/v1/user/starred and private issue titles through /api/v1/user/times. The disclosure depends on relationships or tracked-time entries created before access was revoked.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00281 20th percentileScored 2026-11-07
Fix Fixed code.gitea.io/gitea (Go): 1.27.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
GiteaGitea1.25.4—No fix listedCNA
—code.gitea.io/gitea (Go)before 1.27.01.27.0Patch availableGHSA-qf2f-qh6p-7v89
  • Gitea VendorGitea Affected 1.25.4 Fixed in — No fix listed CNA
  • code.gitea.io/gitea (Go) Vendor— Affected before 1.27.0 Fixed in 1.27.0 Patch available GHSA-qf2f-qh6p-7v89

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*——Gitea
  • cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:* Versions — — ·Gitea

Remediation

Use code.gitea.io/gitea version 1.27.0, which fixes this flaw. The sources list no fixed version for Gitea.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

  • Fix · GHSA-qf2f-qh6p-7v89 code.gitea.io/gitea (Go) Fixed in 1.27.0 Advisory →

Timeline

  1. 2026-10-14 Threatist record created from CVE-2026-59766

References

Patch 1

Advisory 1

Other 2

  • TI-2026-42785 Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation. KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-42033 Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts CVSS 3.1CRITICAL 9.8
  • TI-2026-40842 Privilege Escalation via Access Token Scope Escalation in API CVSS 3.1CRITICAL 9.8
  • TI-2026-16922 Gitea Docker image trusts spoofable reverse-proxy headers by default CVSS 3.1CRITICAL 9.8
  • TI-2026-42043 Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting CVSS 3.1CRITICAL 9.1
  • TI-2026-40381 OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes CVSS 3.1CRITICAL 9.1
See all 240 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences