CVE-2026-129525 json
Gitea pull request disclosure to members with access to issues only
published 2d ago modified yesterday also EUVD-2026-126133 , GHSA-qrrc-h266-v49p
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository go-gitea/gitea. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go gitea.dev 28.4.0
- Gitea Gitea 28.4.0
- github.com/go-gitea/gitea#39839 pull request
- github.com/go-gitea/gitea#39847 pull request
- github.com/go-gitea/gitea#39885 pull request
- github.com/go-gitea/gitea#39938 pull request
- github.com/go-gitea/gitea#40192 pull request
- github.com/go-gitea/gitea#40375 pull request
- github.com/go-gitea/gitea/releases/tag/v28.4.0 release
Is CVE-2026-129525 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | gitea.dev | <=28.3.0 |
28.4.0 |
Affected products
- Gitea Gitea
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
-
github.com
/go-gitea/gitea/pull/39839
patch
-
github.com
/go-gitea/gitea/pull/39847
patch
-
github.com
/go-gitea/gitea/pull/39885
patch
-
github.com
/go-gitea/gitea/pull/39938
patch
-
github.com
/go-gitea/gitea/pull/40192
patch
-
github.com
/go-gitea/gitea/pull/40375
patch
-
github.com
/go-gitea/gitea/security/advisories/GHSA-qrrc-h266-v49p
vendor-advisory, advisory
-
blog.gitea.com
/release-of-28.4.0/
release-notes
-
github.com
/go-gitea/gitea/releases/tag/v28.4.0
release-notes
Sources
- CVE List CVE-2026-129525
- NVD CVE-2026-129525
- Maintainer advisory GHSA-qrrc-h266-v49p
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of go-gitea/gitea published their own advisory on GitHub. Reviewed sources take precedence over it.