/

CVE-2026-58417

Severity:

HIGH RISK

(7.5)

Broken Access Control (CWE-284) in Organization API

CVE-2026-58417

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized Information Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A REST API access-control vulnerability exposes membership information for private organizations to users who should not be able to view it. An attacker may be able to learn the identities or membership relationships of private organizations when authorization checks do not properly restrict the response.

Affected context

The issue occurs in REST API endpoints that return organization membership data for private organizations. It becomes risky when endpoint authorization or object-level access checks do not consistently verify that the requester is allowed to access the organization and its membership details.

Exploit preconditions

  • Attack surface: REST API endpoints exposing organization or membership information
  • Required access: Access to invoke the affected API endpoint; valid authentication may or may not be required depending on deployment policy
  • Trigger point: A request that retrieves membership data for a private organization
  • Why exploitation is possible: The API may disclose protected organization membership information without adequately enforcing the target organization's privacy and authorization requirements

Why this happens

The underlying bug is an authorization failure in which the API treats a request as permitted without sufficiently checking whether the requester may access the targeted private organization's membership data. This maps to CWE-284: Improper Access Control, where security restrictions are missing, inconsistent, or applied to the wrong resource or user context.

Potential impact

  • Unauthorized disclosure of private organization membership
  • Exposure of user identities and organizational relationships
  • Privacy violations and targeted social-engineering risk
  • Discovery of private organizations or their participants
  • Increased risk of follow-on attacks against disclosed accounts or organizations

General mitigation guidance

Mitigation typically focuses on enforcing authorization at the resource and object level for every organization-membership response.

Common defensive patterns include:

  • Denying access by default for private organization data
  • Verifying the requester's relationship and permissions for the specific organization
  • Applying the same authorization policy across list, detail, search, and indirect lookup endpoints
  • Returning only the minimum membership data required for an authorized use case
  • Avoiding reliance on client-side filtering or obscurity of organization identifiers
  • Testing authorization behavior with users, roles, and organization states that should be denied

How teams detect issues like this

Organizations commonly detect broken access control through:

  • Static analysis and code review checks for missing object-level authorization
  • Review of REST handlers, serializers, and query filters that return organization or membership data
  • Negative authorization tests using users with no relationship to private organizations
  • API gateway and application policy checks that require authorization decisions before sensitive data retrieval
  • Monitoring for unusual enumeration of organization identifiers or repeated membership queries

Automated security testing and review tools can help identify inconsistent authorization enforcement across related endpoints.

Sources

SourceLink
blog.gitea.comblog.gitea.com/gitea-1.27.0-is-released/
github.comgithub.com/go-gitea/gitea/releases/tag/v1.27.0
github.comgithub.com/go-gitea/gitea/security/advisories/GHSA-jr5x-6h83-wrxf

Frequently asked

questions

Yes, it may be remotely exploitable through the affected REST API when the endpoint is reachable and its authorization checks allow an unauthorized requester to receive private membership data.

Not necessarily. The required access depends on the API's authentication policy, but even authenticated users may be unauthorized to view the targeted organization.

Enforce deny-by-default, object-level authorization for the specific private organization before retrieving or serializing membership information.

Maintain centralized authorization policies, minimize sensitive API responses, and include automated negative tests for cross-user and cross-organization access.

Find out what's already
exploitable in your codebase.