gitlab-component

gitlab-component Getting started To make it easy for you to get started with GitLab, here's a list of recommended next steps. Already a pro? Just edit this README.md and make it your own. Want to make it easy? Use the template at the bottom! Add your files Create or upload files Add files using t...

Firmware-CVE-2025-7545

Preparing to download the repository 1. Update packages: sudo apt-get update 2. If necessary, install git: sudo apt install -y git Downloading the repository, installing the vulnerable Binutils, and setting up the environment 1. Download the repository: git clone...

CVE-2025-13486.-CVE-2025-13486

This repository does not have a README...

asdsadsadasdasdsadsad

This repository does not have a README...

PT-2026-107542

Name of the Vulnerable Software and Affected Versions @backstage/plugin-scaffolder-backend-module-confluence-to-markdown versions prior to 0.3.25 Description Improper repository path validation in a scaffolder backend module allows an authenticated user who can execute an affected template and...

PT-2026-107484

Name of the Vulnerable Software and Affected Versions GitAhead versions prior to 2.7.2 Description On macOS, a command injection issue exists where repository filenames are interpolated without proper escaping into the Show in Finder AppleScript. An attacker can commit a file with a path containi...

CVE-2026-97208

The Gitea API endpoint for creating push mirrors POST /api/v1/repos/owner/repo/pushmirrors checked only whether mirroring was enabled and not the mirror DISABLENEWPUSH setting that the web interface enforces. A repository administrator could therefore create new push mirrors on instances where th...

CVE-2026-89182

With repository FORCEPRIVATE = true, Gitea creates new repositories as private, but the post-receive hook still applied the repo.private=false push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instan...

CVE-2026-104633

When migrating a repository from another Gitea instance, Gitea used the page size reported in the source server's API settings to end its paginated downloads. A source that reported maxresponseitems as 0 made these loops run indefinitely and grow server memory until it was exhausted. Any user who...

EUVD-2026-94065

With repository FORCEPRIVATE = true, Gitea creates new repositories as private, but the post-receive hook still applied the repo.private=false push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instan...

CVE-2026-89182

With "repository FORCEPRIVATE = true", Gitea creates new repositories as private, but the post-receive hook still applied the "repo.private=false" push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the...

CVE-2026-89182

A flaw in Gitea allows authenticated users with repository creation privileges to bypass instance privacy policies. When [repository] FORCE_PRIVATE = true is enabled, the post-receive hook incorrectly applies the repo.private=false push option to empty repositories created via push. This allows u...

CVE-2026-89182 Gitea push-to-create bypass of FORCE_PRIVATE policy

With repository FORCEPRIVATE = true, Gitea creates new repositories as private, but the post-receive hook still applied the repo.private=false push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instan...

CVE-2026-89182 Gitea push-to-create bypass of FORCE_PRIVATE policy

With repository FORCEPRIVATE = true, Gitea creates new repositories as private, but the post-receive hook still applied the repo.private=false push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instan...

CVE-2026-104633 Gitea migration memory exhaustion from zero page size

When migrating a repository from another Gitea instance, Gitea used the page size reported in the source server's API settings to end its paginated downloads. A source that reported maxresponseitems as 0 made these loops run indefinitely and grow server memory until it was exhausted. Any user who...

CVE-2026-104633 Gitea migration memory exhaustion from zero page size

When migrating a repository from another Gitea instance, Gitea used the page size reported in the source server's API settings to end its paginated downloads. A source that reported maxresponseitems as 0 made these loops run indefinitely and grow server memory until it was exhausted. Any user who...

EUVD-2026-94062

When migrating a repository from another Gitea instance, Gitea used the page size reported in the source server's API settings to end its paginated downloads. A source that reported maxresponseitems as 0 made these loops run indefinitely and grow server memory until it was exhausted. Any user who...

CVE-2026-104633

A flaw in Gitea allows for a Denial of Service (DoS) via memory exhaustion during repository migrations from another instance. The vulnerability occurs because Gitea relies on the source server's reported max_response_items (or max_response_items) to determine the end of paginated downloads. If a...

EUVD-2026-94053

The Gitea API endpoint for creating push mirrors POST /api/v1/repos/owner/repo/pushmirrors checked only whether mirroring was enabled and not the mirror DISABLENEWPUSH setting that the web interface enforces. A repository administrator could therefore create new push mirrors on instances where th...

CVE-2026-97208 Gitea push mirror API bypass of DISABLE_NEW_PUSH policy

The Gitea API endpoint for creating push mirrors POST /api/v1/repos/owner/repo/pushmirrors checked only whether mirroring was enabled and not the mirror DISABLENEWPUSH setting that the web interface enforces. A repository administrator could therefore create new push mirrors on instances where th...