---
id: "CVE-2026-129525"
page: "https://infrastack.ai/live/CVE-2026-129525"
kind: "vulnerability"
aliases: ["CVE-2026-129525", "GHSA-qrrc-h266-v49p"]
title: "Issues-only members can read pull request data through /issues/{index}"
severity: "medium"
cvss: 4.3
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "gitea.dev", "fixed": ["28.4.0"], "affected": "<= 28.3.0", "ecosystem": "go"}]
ecosystems: ["go"]
tags: ["cwe-862", "gitea", "package", "private-repos", "self-hosted"]
not_affected_if: ["gitea-28.4.0-or-later", "no-split-unit-permissions", "public-repos-only"]
published_at: "2026-11-15T21:03:12+00:00"
first_seen_at: "2026-11-15T21:12:47+00:00"
updated_at: "2026-11-15T21:14:12+00:00"
sources: [{"source": "ghsa-repo", "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-qrrc-h266-v49p", "first_seen_at": "2026-11-15T21:12:47+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-129525", "first_seen_at": "2026-11-15T22:40:23+00:00"}]
exploit_sources: []
---

# Issues-only members can read pull request data through /issues/{index}

Link for people: https://infrastack.ai/live/CVE-2026-129525 (this .md is for agents)

Gitea's /issues/{index} API handlers load pull requests without checking the repository unit, so a private-repo member with Issues access but no Pull Requests access can read pull request comment bodies and other metadata. An attacker needs to be an authenticated repository member with access through another unit; attachment contents, pull request bodies and inline review comments were not exposed in the report.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- go:gitea.dev affected <= 28.3.0 fixed 28.4.0

## How to check

- Check the Gitea version with `gitea --version` or the footer of the web UI; versions `28.3.0` and earlier are affected.
- Review which private repositories grant members Issues access without Pull Requests access, since that is the configuration the flaw needs.

## Fix

- Gitea: upgrade to `28.4.0`.

## Timeline

- 2026-11-15T21:12:47+00:00 ghsa-repo https://github.com/go-gitea/gitea/security/advisories/GHSA-qrrc-h266-v49p
- 2026-11-15T22:40:23+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-129525

## Documents

- [advisory] Maintainer's advisory: github.com https://github.com/go-gitea/gitea/security/advisories/GHSA-qrrc-h266-v49p
- [fix] Release notes: github.com https://github.com/go-gitea/gitea/releases/tag/v28.4.0

## From the sources

## Affected versions

Reproduced on Gitea `v1.27.1` and on `main` at commit
`298d73cde6bcb36de6cc24dc436074fb0c8b1a39`.

## Test setup

Official `gitea/gitea:1.27.1` Linux container with SQLite. `INSTALL_LOCK`, the database path,
and a loopback `ROOT_URL` were set only to automate installation. No security-relevant default
was changed.

## Summary

Several `/issues/{index}` API handlers load an issue or pull request from Gitea's shared index
namespace without checking which repository unit it belongs to. In a private repository, a
member with Issues access but no Pull Requests access can therefore read pull request data.

The clearest example is the timeline endpoint: for the same token and pull request,
`GET /issues/{index}/timeline` returns comment bodies while the guarded sibling
`GET /issues/{index}/comments` returns 404.

## Root cause

The `/issues` route group is guarded by `mustEnableIssuesOrPulls`
(`routers/api/v1/api.go:769` and `:1568-1668`), which allows callers who can read either unit.
After resolving `{index}`, these handlers do not call
`CanReadIssuesOrPulls(issue.IsPull)`:

- `ListIssueCommentsAndTimeline` — `routers/api/v1/repo/issue_comment.go:123`
- `GetIssueAttachment` and `ListIssueAttachments` —
  `routers/api/v1/repo/issue_attachment.go:25` and `:74`
- `ListIssueLabels` — `routers/api/v1/repo/issue_label.go:21`
- `setIssueSubscription`, `CheckIssueSubscription`, and `GetIssueSubscribers` —
  `routers/api/v1/repo/issue_subscription.go:106`, `:157`, and `:215`

The adjacent `ListIssueComments` handler performs the missing check at
`routers/api/v1/repo/issue_comment.go:76`.

## Impact

An Issues-only member can read pull request comment bodies. The other confirmed effects are
limited to attachment metadata, label associations, subscriber identities, subscription state,
and setting or clearing watch state. Attachment contents, the pull request body, and inline
review comments were not exposed. Content-writing endpoints remained denied.

The attacker must already be an authenticated repository member with access through another
unit.

## Suggested fix

After resolving `{index}`, call `CanReadIssuesOrPulls(issue.IsPull)` in each handler. A shared
authorized loader for issue and pull request indices would make the check harder to omit.

## Relationship to prior advisories

CVE-2026-27783 (GHSA-3fwp-p5rj-2pxf, fixed in `v1.26.2`) covered missing repository-unit route
guards on the issue-template API. This report affects different handlers: the route admits
Issues-or-Pull Requests users, but the resolved object's unit is never checked.

## AI-tool disclosure

I used an LLM to help identify candidate authorization gaps. I reproduced the behavior manually
against local Gitea instances and checked the report against the source at the tested commit.

---

## Also covers (added by the Gitea maintainers)

The same missing `CanReadIssuesOrPulls(issue.IsPull)` check was reported in later advisories, which were closed as duplicates of this one. The fix must cover these too:

- `POST` / `DELETE /repos/{owner}/{repo}/issues/{index}/reactions` (`changeIssueReaction`): a user who can read only one of the Issues / Pull Requests units can add or remove reactions on an object of the other unit.
- `GET /repos/{owner}/{repo}/issues/{index}/times` (`ListTrackedTimes`): returns the tracked times of a pull request to an Issues-only user.
- Web route `GET /{owner}/{repo}/issues/search?type=pulls`: returns pull request titles and bodies to an Issues-only member. The `type` / `isPull` filter has to be limited to the units the user can read, as the API's `ListIssues` already does. This route is not under the API `/issues/{index}` group, so it needs its own fix.
- The reverse direction: a user who can read only Pull Requests can act on issues through the same handlers.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
