Gitea private pull request disclosure on project boards
Affects Gitea project boards showing private pull requests that are referenced by issues, in versions up to 28.2.0. Fixed in 28.3.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 7/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 28.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Gitea, the self-hosted Git service, is affected through its project boards feature. A private pull request that references an issue on a board could expose the private repository's path and the pull request's number, title, and state to anyone who can view that board, including anonymous visitors on public boards.
Read the original 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.
What to do
Upgrade to a fixed version: 28.3.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- gitea.dev
fixed in 28.3.0
Evidence 5
- Advisory
- Patch
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119533
What does this mean?
A private pull request that references an issue on a project board can be shown to visitors who cannot read that pull request. Those visitors can see the private repository name, the pull request number and title, and whether it is open, closed, or merged. This includes anonymous visitors on a public board.Source: github.com
Am I affected, and how do I check?
The affected range runs from the earliest Gitea release up to 28.2.0, and the fix is in 28.3.0. The advisory specifically names project boards in Gitea 28.1.0. To check an installation, compare its Gitea version with this range and see whether it uses project boards that reference private pull requests.Source: github.com
What should I do about it?
Upgrade Gitea to version 28.3.0 or later, which contains the fix.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data