CVE-2026-120725 in Giteainfo

Summary

by MITRE • 11/16/2026

With `REQUIRE_SIGNIN_VIEW = true`, the Git LFS endpoints still answered unauthenticated requests for repositories that are not private. An anonymous client who knows the path of such a repository and the SHA-256 of an LFS object could download the object, and could use the batch endpoint to test whether an object exists. The Git LFS endpoints now require authentication when sign-in is required to view the instance.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/16/2026

The vulnerability described involves a misconfiguration or logic error in the access control mechanisms of Git Large File Storage (LFS) endpoints within a repository hosting platform, specifically when the global setting REQUIRE_SIGNIN_VIEW is enabled. This configuration parameter is designed to enforce authentication for all users attempting to view any content on the instance, effectively turning the entire service into a private environment where anonymous access should be denied by default. However, under specific conditions involving non-private repositories, this enforcement was bypassed due to an inconsistency in how permission checks were applied across different endpoints and repository visibility states.

The technical flaw centers on the authentication gatekeeping logic for Git LFS operations. When REQUIRE_SIGNIN_VIEW is set to true, the system correctly restricts access to standard web views of code and issues. However, the API endpoints responsible for handling Git LFS requests failed to inherit this global restriction strictly enough when interacting with repositories that were explicitly marked as public or non-private by their owners. This created a discrepancy where the repository metadata indicated open access, while the instance-wide policy demanded authentication. The system prioritized the local repository visibility setting over the global security posture in these specific LFS endpoints, allowing unauthenticated HTTP requests to proceed without triggering an authorization failure.

The operational impact of this vulnerability is significant for organizations relying on Git LFS to store large binary assets such as compiled binaries, datasets, or media files. An anonymous attacker who possesses knowledge of a repository's path and the SHA-256 hash of a specific LFS object can directly download that object without any credentials. This capability effectively nullifies the confidentiality protections intended by the REQUIRE_SIGNIN_VIEW setting for public repositories. Furthermore, because Git LFS provides batch endpoints to check for the existence or status of multiple objects at once, an attacker could leverage these endpoints to perform enumeration attacks. By submitting batches of known hashes, an adversary can determine which specific large files exist within a repository, thereby gaining intelligence about the contents and potentially identifying sensitive artifacts that were not intended to be publicly accessible in terms of their metadata or existence proof.

This behavior aligns with CWE-284 Improper Access Control, as the application failed to enforce consistent access restrictions across different components of its architecture. It also relates to CWE-601 URL Redirection and other related issues if the path knowledge is derived through enumeration, but primarily it represents a failure in enforcing authentication policies uniformly. In terms of MITRE ATT&CK, this vulnerability facilitates Data from Information Repositories by allowing unauthorized retrieval of stored data objects. The ability to test for object existence also supports Reconnaissance activities, specifically Resource Development or Collection phases where an attacker maps out available resources within a target environment without triggering alerts associated with failed login attempts.

To mitigate this issue, the platform has implemented a fix that enforces authentication requirements on Git LFS endpoints whenever REQUIRE_SIGNIN_VIEW is enabled, regardless of the individual repository's visibility status. Administrators should ensure their instance configuration correctly reflects their security posture and verify that all API endpoints adhere to global access control policies. For users managing repositories, it is critical to understand that marking a repository as public does not exempt its LFS objects from instance-wide authentication rules when such rules are active. Regular audits of endpoint behavior against configured security settings can help identify similar inconsistencies in other services or future updates before they are exploited by malicious actors seeking unauthorized access to large file storage systems.

Responsible

Gitea

Reservation

11/15/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!