CVE-2026-129525

Gitea pull request disclosure to members with access to issues only

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The flaw hides in several API and web endpoints that handle both issues and pull requests without verifying which type the resource belongs to. A user who can read only a repository’s issues can therefore access pull‑request information (timeline, attachments, labels, subscriptions, tracked times, reactions) through the issue sub‑resources, and can list pull requests via the repository’s issue‑search and milestone pages; the same privilege inversion applies from pull‑requests to issues. This permissive access turns an issue‑only reader into an unintended pull‑request reader, exposing code review details, attachments, and other potentially sensitive data. The vulnerability is a classic example of an authorization bypass that leads to confidential information leakage, described by CWE-862.

Affected Systems

The issue affects installations of Gitea before the security fixes released in API patches 28.2.0 and 28.3.0 and the UI search/milestone patch in 28.4.0. All affected Gitea instances that have not applied these updates, regardless of other configuration, are at risk, especially repositories where users have read access to issues but not to pull requests. The vendor affected is the Gitea project, and the fix is delivered in the 28.2.0+ releases.

Risk and Exploitability

Because the flaw is exercised through ordinary API calls and web page requests, an authenticated attacker with read‑issue permissions can simply issue a request to the vulnerable endpoints or navigate the web UI to trigger the disclosure. The legitimate use of the API for issue queries is a likely attack vector; there is no known exploitation documented, and the EPSS score is not available. Even without a public exploit, the vulnerability allows an attacker to gain controlled knowledge of pull‑request content, developer identities, and review history. The vulnerability does not require privileges beyond those granted to normal issue readers, thereby widening the attack surface. Consequently, the risk is elevated for any environment that allows issue visibility without equivalent pull‑request restrictions.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to at least version 28.4.0, which includes the necessary access‑control checks for both API and web interfaces.
  • If a quick upgrade is not feasible, re‑assign users who should only read issues to a role that explicitly excludes pull‑request visibility, and disable pull‑request search for those roles where possible.
  • Audit access logs for any unexpected API calls that may indicate the exploitation of unpatched instances or misconfigured permissions.

Generated by OpenCVE AI on November 15, 2026 at 23:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description 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.
Title Gitea pull request disclosure to members with access to issues only
Weaknesses CWE-862
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 15, 2026, 9:14 PM
Reserved
Nov 15, 2026, 8:31 PM
Status
Deferred
Published
Nov 15, 2026, 10:17 PM
Modified
Nov 15, 2026, 10:17 PM