CVE-2026-129525 in Giteainfo

Summary

by MITRE • 11/16/2026

Several endpoints that work on both issues and pull requests did not check which of the two the addressed item is. A user who can read a repository's issues but not its pull requests could read pull request data through the issue sub-resources of the API (timeline, attachments, labels, subscriptions, tracked times and reactions), and list pull requests through the repository's issue search and milestone pages; the same applied in the other direction. These endpoints now check read access to the unit the item belongs to. The API endpoints were fixed in 28.2.0 and 28.3.0, the search and milestone pages in 28.4.0.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/16/2026

The vulnerability described constitutes an authorization bypass within a software development platform's application programming interface and user interface components. Specifically, several endpoints designed to handle both issues and pull requests failed to enforce distinct access control checks for each resource type. This architectural flaw allowed users with read permissions on repository issues but lacking explicit permission to view pull requests to indirectly access sensitive pull request data. The affected resources included timeline events, attachments, labels, subscriptions, tracked times, and reactions associated with pull requests. By exploiting the shared endpoint logic, an attacker could retrieve detailed metadata and activity logs intended only for users with broader repository privileges, thereby violating the principle of least privilege.

In addition to direct API access, this authorization flaw extended to user-facing features such as issue search functionality and milestone pages. These interfaces utilized underlying data queries that did not adequately distinguish between issues and pull requests when filtering results based on user permissions. Consequently, a user restricted from viewing pull requests could still discover their existence and potentially view associated information through these aggregated views. This lateral access vector enabled unauthorized enumeration of repository activities and project planning details, which are typically considered sensitive operational data within collaborative development environments.

The technical root cause lies in the implementation of resource-specific authorization checks. The system relied on a unified handler for both issue and pull request entities without verifying that the requesting user possessed specific read rights for the particular unit type being accessed. This oversight meant that permission grants for one entity type were erroneously applied to another, creating an implicit trust relationship between distinct security boundaries. Such flaws are characteristic of improper access control vulnerabilities where identity verification succeeds but authorization validation fails due to insufficient granularity in permission checks.

From a risk perspective, this vulnerability facilitates information disclosure and unauthorized data aggregation. Attackers can leverage the exposed pull request details to map out development workflows, identify active contributors, or gather context for further social engineering attacks. The exposure of timeline events and attachments may reveal internal discussions, code review comments, or confidential documents attached during the review process. This undermines the confidentiality guarantees expected by repository owners and collaborators who rely on granular permission settings to protect sensitive project information from unauthorized parties within the same organization.

To mitigate this vulnerability, administrators must ensure that all instances of the affected software are upgraded to version 28.4.0 or later. The API endpoints were patched in versions 28.2.0 and 28.3.0, while the search and milestone pages required updates included in version 28.4.0. This upgrade enforces strict separation of access controls between issues and pull requests, ensuring that users can only interact with resources for which they have been explicitly granted permission. Organizations should verify their deployment versions immediately to prevent potential exploitation by internal or external actors seeking unauthorized access to repository data.

This incident aligns with Common Weakness Enumeration category CWE-269, which addresses Improper Privilege Management, specifically the failure to enforce proper authorization checks for different resource types within a single system component. It also relates to ATT&CK technique T1078, Valid Accounts, as it involves using legitimate user credentials to access resources beyond their authorized scope through misconfigured permissions. The resolution highlights the importance of implementing granular role-based access control mechanisms that explicitly validate permissions against specific entity types rather than relying on broad repository-level or issue-specific grants.

Responsible

Gitea

Reservation

11/15/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!