Private org member list leaked via /members API endpoint — incomplete fix for PR #38145
euvd · EUVD-2026-58155 · Published
No access to your tenant or devices. Every item links to its source. What this means
Private org member list leaked via /members API endpoint — incomplete fix for PR #38145
Read the publisher's advisoryPrivate org member list leaked via /members API endpoint — incomplete fix for PR #38145
Read the publisher's advisoryPrivate org member list leaked via /members API endpoint — incomplete fix for PR #38145
Read the publisher's advisory## Summary PR #38145 fixed ListPublicMembers and IsPublicMember but missed ListMembers. Any authenticated user can enumerate ALL members (not just public ones) of a private organization. ## Affected Versions <= v1.26.4 (latest) and main branch ## Root Cause routers/api/v1/org/member.go — ListMembers(): // Missing check: if !organization.HasOrgOrUserVisible(ctx, ctx.Org.Organization.AsUser(), ctx.Doer) { ctx.APIErrorNotFound() return } ## Proof of Concept # Setup: privateorg (private), alice = member, bob = outsider # Bob lists ALL members of private org curl -s "http://gitea/api/v1/orgs/privateorg/members" \ -H "Authorization: token BOB_TOKEN" # Result: HTTP 200 [{"login":"alice","email":"[email protected]",...}] # Expected: HTTP 404 ## Note This is an incomplete fix variant of PR #38145. That PR fixed public_members endpoints only. ListMembers (/orgs/{org}/members) remains unpatched. ## Fix Add to ListMembers(): if !organization.HasOrgOrUserVisible(ctx, ctx.Org.Organization.AsUser(), ctx.Doer) { ctx.APIErrorNotFound() return }
Read the publisher's advisoryGitea: Private org member list leaked via /members API endpoint — incomplete fix for PR #38145 in gitea.dev
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2026-58155 · Published
euvd · EUVD-2026-58155 · Published
euvd · EUVD-2026-58155 · Published
euvd · EUVD-2026-58155 · Published
euvd · EUVD-2026-58155 · Published
euvd · EUVD-2026-58155 · Published
euvd · EUVD-2026-58155 · Published
euvd · EUVD-2026-58155 · Published
euvd · EUVD-2026-58155 · Published
euvd · EUVD-2026-58155 · Published
euvd · EUVD-2026-58155 · Published
euvd · EUVD-2026-58155 · Published
nvd · CVE-2026-58427 · Published
osv · GHSA-prr9-9mp4-5gp2 · Published
osv · GO-2026-6068 · Published
cve-program · CVE-2026-58427 · Published