Descripción
GitLab Community Edition and Enterprise Edition contiene una vulnerabilidad de recorrido de directorios (path traversal) que permite a un usuario no autenticado leer archivos arbitrarios debido a una restricción incorrecta de rutas y a la falta de aplicación de autenticación en la API de commits del repositorio.
Acción recomendada
Aplicar las mitigaciones del fabricante y revisar los equipos afectados en busca de señales de compromiso (triaje forense) antes de darlos por remediados. Evaluar la exposición a internet de cada activo para priorizar la aplicación de parches. En servicios en la nube, seguir las recomendaciones de seguridad del proveedor; si no hay mitigaciones disponibles, discontinuar el uso del producto.
Referencia de CISA para agencias federales de EE. UU.: BOD 26-04.
Referencias
- Aviso de docs.gitlab.com docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/
- BOD 26-04 cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updat…
- Requisitos de triaje forense cisa.gov/news-events/directives/bod-26-04-implementation-guidance-pri…
- Ficha en NVD (NIST) nvd.nist.gov/vuln/detail/CVE-2026-85706
Ver el texto original en inglés (CISA)
GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability
GitLab Community Edition and Enterprise Edition contains a path traversal vulnerability that allows an unauthenticated user to read arbitrary files due to an improper path confinement and missing authentication enforcement in the repository commits API.
Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Notes: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/ ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-85706
Otras vulnerabilidades de GitLab en el catálogo
- CVE-2021-22175 GitLab Server-Side Request Forgery (SSRF) Vulnerability Alta 18-02-2026
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) Vulnerability Alta 03-02-2026
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control Vulnerability Alta 01-05-2024
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution Vulnerability Alta 03-11-2021