# CVE-2026-129525: Gitea pull request disclosure to members with access to issues only

> Gitea users with issue access can read pull request data and list pull requests through issue sub-resources and search.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-qrrc-h266-v49p

## What is CVE-2026-129525?

CVE-2026-129525 is a medium-severity missing authorization vulnerability in Gitea, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-129525?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-129525?

No fix has been published for CVE-2026-129525 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129525 being exploited?

There is no known exploitation of CVE-2026-129525 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129525 and fix it if it is affected.

What it is: CVE-2026-129525 is a medium-severity missing authorization vulnerability in Gitea, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129525 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Gitea. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129525/ (Markdown: https://insights.sbomify.com/CVE-2026-129525/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129525
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129525
- OSV: https://osv.dev/vulnerability/CVE-2026-129525

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129525/
Summaries are generated and may contain mistakes; the official description above is the record.
