BaseFortify

Publication date: 2026-01-22

Last updated on: 2026-01-29

Assigner: Gitea Limited

Description

Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-01-22

Last Modified

2026-01-29

Generated

2026-07-06

AI Q&A

2026-01-23

EPSS Evaluated

2026-07-05

NVD

CVE-2026-20800

Affected Vendors & Products

Vendor	Product	Version / Range
gitea	gitea	to 1.25.4 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-200	The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

Executive Summary

This vulnerability in Gitea's notification API occurs because it does not re-check repository access permissions when providing notification details. As a result, if a user's access to a private repository is revoked, they may still be able to see issue and pull request titles from notifications they received before losing access.

Impact Analysis

The vulnerability can lead to unauthorized disclosure of information, as users who no longer have access to a private repository might still view sensitive issue and pull request titles. This could expose confidential project details or development activities to unintended parties.

Hi! I’m here to help you understand CVE-2026-20800. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70