CVE-2025-68941
Unknown Unknown - Not Provided

Improper Access Control in Gitea API Allows Data Exposure

Publication date: 2025-12-26

Last updated on: 2025-12-26

Assigner: MITRE

Description
Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2025-12-26
Last Modified
2025-12-26
Generated
2026-07-06
AI Q&A
2025-12-26
EPSS Evaluated
2026-07-05
NVD
CVE-2025-68941
EUVD
EUVD-2025-205408

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
gitea gitea 1.22.3

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Gitea before version 1.22.3 involves improper handling of API tokens that are limited to the "public only" scope. Specifically, tokens assigned with this limited scope could incorrectly gain access to private resources, bypassing intended access restrictions. The issue was due to a bug in the enforcement of token scope permissions, which was fixed by modifying API routes and code to correctly restrict such tokens to public resources only. [1]

Impact Analysis

The vulnerability can lead to unauthorized access to private resources in Gitea when using API tokens that should only have public access. This means that an attacker or user with a token scoped for public resources might be able to access private data or perform actions beyond their intended permissions, potentially exposing sensitive information or compromising repository security. [1, 2]

Mitigation Strategies

The immediate step to mitigate this vulnerability is to upgrade Gitea to version 1.22.3 or later, which includes the security fix addressing the token scope handling issue. This update corrects the enforcement of the 'public only' token scope to prevent unauthorized access. Applying this update as soon as possible will mitigate the risk. [2, 3]

Chat Assistant

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

EPSS Chart