CVE-2026-126338
Gitea private diff disclosure through code comment replies
Description
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.
INFO
Published Date :
Nov. 15, 2026, 10:17 p.m.
Last Modified :
Nov. 15, 2026, 10:17 p.m.
Remotely Exploit :
No
Source :
88ee5874-cf24-4952-aea0-31affedb7ff2
Solution
- Ensure review replies target the correct pull request.
- Verify users can only reply to reviews they are authorized for.
- Validate pending review replies are from the author.
- Update review ID validation logic.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-126338.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-126338 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-126338
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-126338 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-126338 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 88ee5874-cf24-4952-aea0-31affedb7ff2
Nov. 15, 2026
Action Type Old Value New Value Added Description 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. Added CWE CWE-639 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/126xxx/CVE-2026-126338.json">CVE-2026-126338</a> Added Reference https://blog.gitea.com/release-of-28.4.0/ Added Reference https://github.com/go-gitea/gitea/pull/40131 Added Reference https://github.com/go-gitea/gitea/pull/40281 Added Reference https://github.com/go-gitea/gitea/releases/tag/v28.4.0 Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-wgx7-537g-xfrg