# CVE-2026-119533: Gitea project boards information disclosure of private pull requests

Source: https://junglewise.ai/threats/cve-2026-119533-repository-and-organization-project-boards-listed-the-pull  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-01. Updated: 2026-11-01  
License: CC BY 4.0 with a link back

CVE-2026-119533 · Severity: info · Published 2026-11-01

Gitea, a self-hosted Git service, exposed information about private pull requests on public project boards. When a private pull request referenced an issue displayed on a board, anyone viewing that board—including anonymous visitors—could see the pull request's title, number, state, and the path to the private repository. This allowed unauthorized access to metadata about private work, potentially revealing internal development details.

Technologies: [Gitea](https://junglewise.ai/threats/technologies/gitea). Vendors: [Gitea](https://junglewise.ai/threats/vendors/gitea).

## Quick answers

**Is CVE-2026-119533 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-119533 being exploited in the wild.

**How severe is CVE-2026-119533?** Informational severity, published 1 November 2026.

**Which products and versions are affected?** Gitea before 28.3.0.

**Is there a fix for CVE-2026-119533?** Yes: fixed in Gitea 28.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-119533 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-119533?** Check whether you run Gitea at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Gitea 28.3.0

## Technical details

Project boards in Gitea loaded linked pull requests without checking viewer permissions, exposing private pull request metadata (title, number, state, repository path) to unauthorized users. The vulnerability affected repository and organization boards when private pull requests mentioned issues on accessible boards. The fix filters out pull requests from repositories where the viewer lacks read access, matching the existing protection on issue detail pages.

## Affected products

- Gitea Gitea before 28.3.0

## Timeline

- 2026-11-01: disclosed
- 2026-11-01: patched

## References

- [https://blog.gitea.com/release-of-28.3.0/](https://blog.gitea.com/release-of-28.3.0/)
- [https://github.com/go-gitea/gitea/pull/40016](https://github.com/go-gitea/gitea/pull/40016)

## Related threats

- [Gitea account takeover via OAuth2 auto-linking](https://junglewise.ai/threats/cve-2026-120263-when-oauth2-client-account-linking-is-set-to-auto-not-the)
- [Gitea limited-visibility profile disclosure via public-only token](https://junglewise.ai/threats/cve-2026-119627-the-web-profile-and-rss-atom-feed-routes-of-users-and)
- [Gitea token scope bypass in web routes](https://junglewise.ai/threats/cve-2026-119625-the-username-web-route-accepted-personal-access-tokens-over-http)
- [Gitea API token scope bypass in repository deletion](https://junglewise.ai/threats/cve-2026-119441-delete-api-v1-orgs-org-repos-deletes-all-repositories-of-an)
- [Gitea REST API archived repository modification bypass](https://junglewise.ai/threats/cve-2026-118504-the-web-interface-blocks-issue-and-pull-request-changes-on)