CVE-2026-58429
Received Received - Intake

Public-Only Personal Access Tokens Bypass in GitHub Organization

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: Gitea Limited

Description
Public-Only Personal access tokens scope bypass in Organization and Permission Endpoints

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-13
Last Modified
2026-08-13
Generated
2026-08-13
AI Q&A
2026-08-13
EPSS Evaluated
N/A
NVD
CVE-2026-58429
EUVD
EUVD-2026-58157

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
CWE-1259 The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability allows a personal access token with a public-only scope in Gitea to bypass intended restrictions and access private organization membership and permission details for the token owner's own account. It affects endpoints like GET /api/v1/user/orgs and GET /api/v1/users/{username}/orgs/{org}/permissions due to inconsistent enforcement of the public-only token restriction.

Detection Guidance

To detect this vulnerability, check Gitea logs for unusual API requests to endpoints like GET /api/v1/user/orgs or GET /api/v1/users/{username}/orgs/{org}/permissions. Monitor for requests using public-only tokens accessing private organization data. Verify if tokens with public-only scope are retrieving private organization membership or permissions.

Impact Analysis

An attacker with a public-only token could enumerate private organizations and retrieve sensitive authorization details such as ownership, admin status, and repository access rights. This weakens least-privilege token delegation and may expose internal organizational structures.

Mitigation Strategies

Upgrade Gitea to version 1.27.0 or later to patch the vulnerability. Review and revoke any public-only tokens that may have accessed private organization data. Implement stricter token scope validation and enforce proper middleware checks for all API endpoints.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-58429. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart