Gitea private diff disclosure through code comment replies
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-639.
Summary
Gitea versions from 1.14.0 before 28.4.0 accept a review ID from a different pull request when replying to a code review comment, through the web form, the API and incoming mail replies. A signed-in user who can access a pull request can reply with the ID of a review in a repository they cannot read, which attaches the new comment to that review and exposes the diff context of the commented lines. The flaw is an authorization bypass through a user-controlled key (CWE-639). The attack is limited to signed-in users with access to the pull request and has a high complexity.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
Description from the CNA
Replying to a code review comment accepted a review ID that belongs to a different pull request, through the web form, the API and incoming mail replies. A signed-in user could reply on a pull request they can access with the ID of a review in a repository they cannot read, and the new comment was attached to that review and received the diff context of the commented lines. Replies are now only accepted for a review of the same pull request, and for a pending review only from its author.
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
Upgrade Gitea to version 28.4.0, which only accepts replies for a review of the same pull request and, for a pending review, only from its author.
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-126338
- 2026-11-16 CVSS score added · CISA ADP
- 2026-11-16 CISA SSVC decision points changed
References
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