Gitea exposes pull request data to users with issue-only access
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-862.
Summary
Several Gitea API endpoints and the repository issue search and milestone pages did not check whether an addressed item was an issue or a pull request. A user with read access to a repository's issues but not its pull requests could read pull request data through these paths, and the same applied in the other direction. An authenticated user with low privileges can exploit this remotely, and the flaw is tracked as CWE-862 (missing authorization).
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Gitea 28.4.0 fixes the issue. The API endpoints were fixed in 28.2.0 and 28.3.0, and the search and milestone pages in 28.4.0, so upgrade to Gitea 28.4.0 or later.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
- Fix · CNA Gitea (Gitea) Fixed in 28.4.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Gitea 28.4.0
19 records Highest priority Priority LOW 19 LOW
Other records, highest priority first
- TI-2026-91976 Command execution in Gitea through repository auto-initializationPriority LOW 39
- TI-2026-91985 Protected file pattern bypass in Gitea with quoted file namesPriority LOW 36
- TI-2026-91982 Gitea missing attempt limit for TOTP passcodesPriority LOW 34
Timeline
- 2026-11-15 Threatist record created from CVE-2026-129525
- 2026-11-16 CVSS score added · CISA ADP
- 2026-11-16 CISA SSVC decision points changed
References
Patch 6
- Fix: go-gitea/gitea pull request #39839
- Fix backport to release/v28: go-gitea/gitea pull request #39847
- Fix: go-gitea/gitea pull request #39885
- Fix backport to release/v28: go-gitea/gitea pull request #39938
- Fix: go-gitea/gitea pull request #40192
- Fix backport to release/v28: go-gitea/gitea pull request #40375
More Gitea vulnerabilities
- TI-2026-42785 Remote code execution in Gitea diffpatch API through Git hooks KEVCVSS 3.1CRITICAL 9.8
- TI-2026-42033 Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts CVSS 3.1CRITICAL 9.8
- TI-2026-40842 Privilege Escalation via Access Token Scope Escalation in API CVSS 3.1CRITICAL 9.8
- TI-2026-16922 Gitea Docker image trusts spoofable reverse-proxy headers by default CVSS 3.1CRITICAL 9.8
- TI-2026-42043 Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting CVSS 3.1CRITICAL 9.1
- TI-2026-40381 OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes CVSS 3.1CRITICAL 9.1
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences