/

CVE-2026-20750

Severity:

CRITICAL RISK

(9.1)

Improper Access Control in Gitea

CVE-2026-20750

Modified

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Project Modification and Cross-Organization Data Tampering

Severity:

CRITICAL RISK

(9.1)

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

Gitea contains an improper access control flaw where project ownership is not correctly validated during organization project operations.

Under certain conditions, a user with write access to a project in one organization may be able to modify projects belonging to a different organization, leading to unauthorized changes across organizational boundaries.

Affected context

This vulnerability affects Gitea instances that use organization-level projects and delegate write access to users or teams.

The issue appears when access checks for project operations rely on incomplete or incorrect validation of the project's owning organization rather than the specific context in which the operation is performed.

Environments with multiple organizations, shared users, and granular project permissions are particularly exposed, as cross-organization operations may be incorrectly permitted.

Exploit preconditions

  • Attack surface: Gitea web UI and API endpoints that handle organization project operations (e.g., creating, editing, or managing project properties and items).
  • Required access: Valid authenticated user account with project write access in at least one organization; no direct membership in the target organization's project is necessarily required.
  • Trigger point: Performing project operations (such as updates or modifications) that are processed without strictly checking that the acting user's permissions match the ownership of the specific project being modified.
  • Why exploitation is possible: The access control logic does not consistently verify that the user's authorization applies to the actual owning organization of the project, allowing operations to be performed on projects in different organizations under certain conditions.

Why this happens

The root cause is an improper access control implementation mapped to CWE-284, where authorization decisions are made using incomplete or context-mismatched checks.

Instead of binding each project operation to the project's true owning organization and verifying the user's rights in that organization, the code path appears to trust broader or indirect assumptions—such as the user's write rights in one organization—to authorize actions across organization boundaries.

This pattern reflects a missing or incorrect enforcement of object-level access rules, where the resource identifier (project) and its ownership (organization) are not consistently bound and validated in every operation path.

Potential impact

  • Unauthorized modification of projects in other organizations, including names, descriptions, and metadata.
  • Tampering with cross-organization project planning, boards, issues linkage, or task tracking.
  • Disruption of workflows and loss of integrity in project management data.
  • Potential leakage of sensitive project structure or metadata through unintended access.
  • Damage to trust boundaries between logically separated organizations within the same Gitea instance.

General mitigation guidance

Mitigation generally focuses on hardening authorization checks and reinforcing resource ownership validation:

  • Ensure that every project operation validates the project's owning organization and confirms that the acting user has appropriate permissions in that specific organization.
  • Apply a strict object-level permission model where each project is treated as a distinct resource tied to an organization, and permissions are resolved per resource rather than by inference.
  • Centralize access control logic so that all project operations go through a consistent authorization layer instead of ad hoc checks scattered across handlers.
  • Limit the breadth of granted roles (e.g., "write" access) to the minimal set of actions necessary and avoid cross-organization assumptions in shared components.
  • Prefer secure-by-default patterns where any ambiguity in ownership or permission resolution results in denial rather than implicit allow.

How teams detect issues like this

Detection strategies may include:

  • Static analysis and code review:
  • Look for project-related operations that do not explicitly validate the organization ID associated with the project before applying changes.
  • Flag any authorization logic that relies on user roles in "some" organization without binding to the specific project owner.
  • Review controller/handler methods and API endpoints dealing with organization projects to ensure they delegate to a centralized authorization service.
  • Policy and configuration checks:
  • Enforce internal policies that require object-level access control for all multi-tenant or multi-organization features.
  • Use automated review tooling or custom linting rules to detect direct database or ORM operations on project entities that bypass access control layers.
  • Runtime monitoring and logging:
  • Enable detailed audit logging for project modifications, including acting user, source organization, and target project's organization.
  • Monitor for patterns where users frequently modify projects outside their primary organization or team scope.

Sources

SourceLink
blog.gitea.comblog.gitea.com/release-of-1.25.4/
github.comgithub.com/go-gitea/gitea/pull/36318
github.comgithub.com/go-gitea/gitea/pull/36373
github.comgithub.com/go-gitea/gitea/releases/tag/v1.25.4
github.comgithub.com/go-gitea/gitea/security/advisories/GHSA-h4fh-pc4w-8w27
access.redhat.comaccess.redhat.com/security/cve/CVE-2026-20750
bugzilla.redhat.combugzilla.redhat.com/show_bug.cgi?id=2432216
security.access.redhat.comsecurity.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-20750.json

Frequently asked

questions

Exploitability is limited to authenticated users who already have write access to at least one organization project, but within such deployments, it may allow those users to impact projects in other organizations, making it serious in multi-tenant instances.

No. The attacker typically only needs standard project write permissions in one organization; elevated or administrative roles are not necessarily required to trigger cross-organization modifications.

Implement strict, centralized authorization checks for every project operation that:

  1. Resolve the actual owning organization of the target project, and
  2. Verify the acting user's permissions within that specific organization before performing any change.

Adopt a consistent object-level access control model, mandate security-focused code reviews for multi-organization features, and incorporate automated checks that flag any resource modification paths bypassing the standardized authorization layer.

Find out what's already
exploitable in your codebase.