CVE-2026-119533
Deferred Deferred - Pending Action

Private Pull Request Exposure in GitHub Project Boards

Publication date: 2026-11-01

Last updated on: 2026-11-01

Assigner: Gitea Limited

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-01
Last Modified
2026-11-01
Generated
2026-11-01
AI Q&A
2026-11-01
EPSS Evaluated
N/A
NVD
CVE-2026-119533

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Gitea Gitea 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Gitea allows public project boards to display details of private pull requests linked to public issues without verifying the viewer's access permissions. It exposes the title, number, state, and repository path of private pull requests to unauthorized users, including anonymous visitors.

Detection Guidance

Check Gitea version with: curl -s http://your-gitea-server/api/v1/version | grep version. If version is <= 28.2.0, the system is vulnerable. Inspect project boards for private pull request details in HTML source or API responses.

Impact Analysis

If you use Gitea project boards, this vulnerability could expose sensitive information about private pull requests to unauthorized users. Attackers might learn details like repository paths, pull request titles, and their open/merged status without accessing the repositories directly.

Compliance Impact

This vulnerability could lead to unauthorized disclosure of sensitive data, potentially violating compliance requirements like GDPR or HIPAA that mandate protection of confidential information. Organizations using Gitea must ensure proper access controls to avoid regulatory penalties.

Mitigation Strategies

Upgrade Gitea to version 28.3.0 or later. Review project boards to ensure no private pull request details are exposed. Verify access controls for project boards and repositories.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-119533. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...