CVE-2026-119533
Gitea private pull request disclosure on project boards
Description
Repository and organization project boards listed the pull requests that reference each issue on the board without checking whether the viewer can read them. When a private pull request mentions an issue on a board the viewer can open, the board revealed the private repository's path and the pull request's number, title and state, to anonymous visitors in the case of a public board. The pull request body, diff and files were not exposed. Boards now skip linked pull requests in repositories where the viewer cannot read pull requests.
INFO
Published Date :
Nov. 1, 2026, 10:18 a.m.
Last Modified :
Nov. 1, 2026, 10:18 a.m.
Remotely Exploit :
No
Source :
88ee5874-cf24-4952-aea0-31affedb7ff2
Affected Products
The following products are affected by CVE-2026-119533
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the system to filter pull requests based on viewer permissions.
- Ensure private repository details are not exposed on public boards.
- Verify access controls for linked pull requests on boards.
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-119533.
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-119533 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-119533
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-119533 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-119533 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. 01, 2026
Action Type Old Value New Value Added Description Repository and organization project boards listed the pull requests that reference each issue on the board without checking whether the viewer can read them. When a private pull request mentions an issue on a board the viewer can open, the board revealed the private repository's path and the pull request's number, title and state, to anonymous visitors in the case of a public board. The pull request body, diff and files were not exposed. Boards now skip linked pull requests in repositories where the viewer cannot read pull requests. Added CWE CWE-862 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/119xxx/CVE-2026-119533.json">CVE-2026-119533</a> Added Reference https://blog.gitea.com/release-of-28.3.0/ Added Reference https://github.com/go-gitea/gitea/pull/40016 Added Reference https://github.com/go-gitea/gitea/pull/40134 Added Reference https://github.com/go-gitea/gitea/releases/tag/v28.3.0 Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-c45m-jm46-mwxg