CVE-2026-58417: Gitea: REST API exposes organization membership of private organizations to public
Summary The endpoint "/orgs/{org}/publicmembers/{username}" + GET exposes organization membership of public members in a private organization. PoC 1. Spin up the nightly container of Gitea. 2. Perform the default installation. 3. Register a new user (let's call this user "user1"). 4. Create a new organization with "private" visibility. We will refer to this organization as "user1org". 5.
Published Jul 21, 2026
Affected packages
gitea.dev
- Ecosystem
- Go
- Affected
- < 1.27.0
- Fixed in
- 1.27.0
- Check
go list -m gitea.dev
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The endpoint "/orgs/{org}/public_members/{username}" + GET exposes organization membership of public members in a private organization.
PoC
- Spin up the nightly container of Gitea.
- Perform the default installation.
- Register a new user (let's call this user "user1").
- Create a new organization with "private" visibility. We will refer to this organization as "user1org".
- Make the user "user1" inside the organization visible.
- Log out and register a new user ("user2").
- Create an access token for "user2" with full access to the API.
- Use the endpoint "/orgs/{org}/public_members/{username}" + GET with the correct username of "user1", organization name, and access token of "user2" to query whether "user1" is a member of the organization. The following curl command demonstrates the usage:
curl -X 'GET' \ 'http://localhost:4700/api/v1/orgs/user1org/public_members/user1' \ -H 'accept: application/json' \ -H 'authorization: token '
- You will receive status code 204, which leaks the organization membership.
Impact
The vulnerability discloses organization membership. An information that is not accessible via the web app (the organization is hidden, and therefore, the organization membership on the user's profile page is also hidden).
Credited to maluff, Sai2r, mgelde.
References
- https://github.com/go-gitea/gitea/security/advisories/GHSA-jr5x-6h83-wrxf
- https://github.com/go-gitea/gitea/pull/38145
- https://github.com/go-gitea/gitea/commit/685b62c60fc595e3612a85f0895471876db56292
- https://github.com/go-gitea/gitea/releases/tag/v1.27.0
- https://github.com/advisories/GHSA-jr5x-6h83-wrxf
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-60004
Gitea: Remote Code Execution via diffpatch Git Hook Installation
critical9.8ExploitedSep 8, 2026CVE-2026-28740
Gitea: Git LFS object reuse allows non-Code access to authorize private source objects
high7.1Jul 21, 2026CVE-2026-56443
Gitea: Token public-only scope bypassed on Limited-visibility owners (Repository + Package categories) — residual after CVE-2026-25714 / PR #37118
medium4.3Jul 21, 2026CVE-2026-56657
Gitea SSH Key Parser Denial of Service
medium6.2Jul 21, 2026CVE-2026-58416
Gitea: Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard)
medium6.3Jul 21, 2026CVE-2026-58420
Gitea: Local File Inclusion via file:// URI in Migration Restore
medium6.7Jul 21, 2026
