BaseFortify

Publication date: 2026-01-22

Last updated on: 2026-06-27

Assigner: Gitea Limited

Description

Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release in a different public repository, making it accessible to unauthorized users.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-01-22

Last Modified

2026-06-27

Generated

2026-07-06

AI Q&A

2026-01-23

EPSS Evaluated

2026-07-05

NVD

CVE-2026-20912

Affected Vendors & Products

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

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-284	The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
CWE-283	The product does not properly verify that a critical resource is owned by the proper entity.
CWE-639	The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

Executive Summary

This vulnerability in Gitea occurs because the software does not properly verify who owns a repository when linking attachments to releases. As a result, an attachment uploaded to a private repository could be linked to a release in a different public repository, potentially exposing private content to unauthorized users.

Impact Analysis

The vulnerability can lead to unauthorized access to private attachments by making them accessible through public repository releases. This could result in sensitive or confidential information being exposed to users who should not have access.

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

0/70