Wiz se unirá a Google Cloud: Haciendo magia juntos

CVE-2026-18491: 
GitLab Análisis y mitigación de vulnerabilidades

Vista general

CVE-2026-18491 is an Incorrect Authorization vulnerability (CWE-863) in GitLab CE/EE affecting all versions from 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. Under certain conditions, an authenticated user holding a granular personal access token with limited scope could authorize Kubernetes API proxy access beyond the token's intended boundaries due to missing granular scope enforcement in the Kubernetes agent proxy-user authorization flow. It was published on November 17, 2026, with patches released in the same GitLab patch cycle. It carries a CVSS v3.1 base score of 4.9 (Medium) (GitHub Advisory, GitLab Patch Release).

Detalles técnicos

The root cause is CWE-863 (Incorrect Authorization): GitLab's Kubernetes agent proxy-user authorization flow fails to properly enforce granular personal access token scope restrictions, allowing a token with limited scope to be used for broader Kubernetes API proxy access than intended. Exploitation requires an authenticated user with a valid granular personal access token; the attacker leverages the missing scope check in the proxy-user authorization flow to issue Kubernetes API requests that exceed the token's defined permissions. Attack complexity is rated High, indicating that specific conditions must be met for exploitation to succeed. No public proof-of-concept code has been identified (GitHub Advisory, GitLab Patch Release).

Impacto

Successful exploitation allows an authenticated attacker to access Kubernetes API resources and perform actions beyond the boundaries of their token's intended permissions, resulting in low confidentiality and low integrity impacts with no availability impact. The changed scope metric indicates that the impact extends beyond the GitLab application itself to connected Kubernetes clusters managed via the GitLab agent. This could expose sensitive Kubernetes workload data or allow unauthorized modifications to cluster resources, depending on the Kubernetes RBAC configuration in place (GitHub Advisory).

Explotabilidad

There is no evidence of active in-the-wild exploitation or publicly available proof-of-concept code for CVE-2026-18491 at this time. The NVD SSVC assessment classifies exploitation as "none" and the attack as non-automatable, reflecting the requirement for an authenticated user and specific conditions. The EPSS score is approximately 0.169%, indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog (GitHub Advisory, GitLab Patch Release).

Pasos de explotación

  1. Reconnaissance: Identify a GitLab CE/EE instance running a vulnerable version (19.2.x before 19.3.9, 19.4.x before 19.4.8, or 19.5.x before 19.5.6) with the Kubernetes agent integration enabled.
  2. Obtain credentials: Authenticate to the GitLab instance and obtain or create a granular personal access token with limited scope (e.g., scoped to a specific project or resource type).
  3. Identify Kubernetes agent proxy endpoint: Locate the Kubernetes agent proxy-user authorization endpoint within the GitLab instance that is used to proxy API requests to connected Kubernetes clusters.
  4. Issue out-of-scope Kubernetes API requests: Use the limited-scope token to send Kubernetes API proxy requests targeting resources or namespaces beyond the token's intended authorization boundaries, exploiting the missing scope enforcement check.
  5. Access unauthorized resources: Receive responses from the Kubernetes API for resources the token should not have access to, potentially reading sensitive workload data or performing unauthorized modifications (GitHub Advisory).

Indicadores de compromiso

  • Logs: GitLab application logs showing Kubernetes agent proxy-user authorization requests from granular personal access tokens accessing resources outside their defined scope; unexpected Kubernetes API calls originating from the GitLab agent proxy for tokens with restricted scopes.
  • Network: Unusual Kubernetes API requests proxied through the GitLab agent to namespaces or resources not associated with the token's intended project or scope.
  • GitLab Audit Events: Audit log entries for Kubernetes agent proxy access events associated with granular personal access tokens, particularly where the accessed resources do not match the token's configured scope.

Mitigación y soluciones alternativas

GitLab has released patched versions addressing this vulnerability: upgrade to GitLab 19.3.9, 19.4.8, or 19.5.6 (or later) depending on your current version. If immediate patching is not possible, administrators should audit all granular personal access tokens in the environment and monitor Kubernetes agent proxy-user authorization logs for suspicious activity. Restricting or temporarily revoking granular personal access tokens with Kubernetes agent proxy access until patching is completed is also advisable (GitLab Patch Release, GitHub Advisory).

Reacciones de la comunidad

Coverage of CVE-2026-18491 appeared as part of broader reporting on GitLab's November 2026 patch release, which addressed 37 security vulnerabilities. Security news outlets including GBHackers and CyberPress covered the patch release, noting the scope of fixes across CI/CD pipelines, GitLab Pages, and the MCP server (GBHackers, CyberPress). No notable individual researcher commentary or significant social media discussion specific to this CVE has been identified.

Recursos adicionales


Fuente: Este informe se generó usando IA

Relacionado GitLab Vulnerabilidades:

CVE ID

Gravedad

Puntuación

Tecnologías

Nombre del componente

Exploit CISA KEV

Tiene solución

Fecha de publicación

CVE-2026-18241HIGH8.2
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoSíNov 17, 2026
CVE-2026-97187HIGH7.6
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoSíNov 17, 2026
CVE-2026-85778MEDIUM6.2
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoSíNov 17, 2026
CVE-2026-16609MEDIUM5.4
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoSíNov 17, 2026
CVE-2026-18491MEDIUM4.9
  • GitLab logoGitLab
  • cpe:2.3:a:gitlab:gitlab
NoSíNov 17, 2026

Evaluación gratuita de vulnerabilidades

Haz un benchmark de tu postura de seguridad en la nube

Evalúa tus prácticas de seguridad en la nube en 9 dominios de seguridad para evaluar tu nivel de riesgo e identificar brechas en tus defensas.

Evaluación de solicitudes

Recursos adicionales de Wiz

Obtén una demostración personalizada

¿Listo para ver a Wiz en acción?

"La mejor experiencia de usuario que he visto en mi vida, proporciona una visibilidad completa de las cargas de trabajo en la nube."
David EstlickCISO
"Wiz proporciona un panel único para ver lo que ocurre en nuestros entornos en la nube."
Adam FletcherJefe de Seguridad
"Sabemos que si Wiz identifica algo como crítico, en realidad lo es."
Greg PoniatowskiJefe de Gestión de Amenazas y Vulnerabilidades