Gitea's starred-repository and tracked-time API endpoints do not re-check current repository permissions before returning data associated with the requesting user.

Code

The project this record applies to. Exploit listings stay in References.

• Repository · github.com

Timeline

Detection, updates, and resolution for this record.

1. Oct 14, 2026 · NIST NVD

   Detected

   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-tim

2. Oct 14, 2026 · NIST NVD

   Updated

   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-tim

Sources

• CVE.orgVulnerability recordCVE-2026-59766

  Official CVE identifier

  cve.org
• FIRST EPSSExploitation probabilityCVE-2026-59766

  30-day exploitation probability 0.3%

  first.org
• NIST NVDVulnerability recordCVE-2026-59766

  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/

  nvd.nist.gov

References

• Reference · github.com
• Reference · github.com