Answer in brief
CVE-2026-126338 records a Unknown severity vulnerability in Gitea private diff disclosure through code comment replies. The current sources do not mark it as known exploited. The current feed maps Gitea/Gitea (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Gitea/Gitea (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Gitea/Giteageneric | >=1.14.0 <28.4.0 | 28.4.0 |
Published upstream
Nov 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.