Esta página ainda não foi traduzida para o seu idioma. Exibindo conteúdo em inglês enquanto trabalhamos nisso.
💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.
CVE-2026-1322: Authorization Bypass in GitLab
Plataforma
gitlab
Componente
gitlab
Corrigido em
18.11.3
CVE-2026-1322 describes an authorization bypass vulnerability within GitLab Community Edition (CE) and Enterprise Edition (EE). This flaw allows an authenticated user possessing a read_api scoped OAuth application to circumvent authorization controls and create issues and add comments to private projects. The vulnerability impacts GitLab versions ranging from 16.0.0 through 18.11.3, with a fix available in version 18.11.3.
Impacto e Cenários de Ataquetraduzindo…
The primary impact of CVE-2026-1322 is the potential for unauthorized access and modification of private project data within GitLab. An attacker leveraging a readapi OAuth application could create issues, add comments, and potentially manipulate project workflows without proper authorization. This could lead to data breaches, intellectual property theft, or disruption of development processes. While the vulnerability requires an existing OAuth application, the ease of creating such applications lowers the barrier to exploitation. The scope of impact is limited to projects where the attacker has access to a readapi OAuth application, but the potential for widespread impact across an organization's GitLab instance remains significant.
Contexto de Exploraçãotraduzindo…
CVE-2026-1322 was published on May 14, 2026. Its severity is rated as Medium (CVSS 6.8). There is no indication of this vulnerability being actively exploited in the wild at this time. Public proof-of-concept (POC) code is not currently available, which may limit immediate exploitation. The vulnerability is not listed on CISA’s Known Exploited Vulnerabilities (KEV) catalog, and EPSS score is pending evaluation.
Inteligência de Ameaças
Status do Exploit
CISA SSVC
Vetor CVSS
O que significam essas métricas?
- Attack Vector
- Rede — explorável remotamente pela internet. Sem acesso físico ou local necessário.
- Attack Complexity
- Alta — exige condição de corrida, configuração não padrão ou circunstâncias específicas.
- Privileges Required
- Baixo — qualquer conta de usuário válida é suficiente.
- User Interaction
- Nenhuma — ataque automático e silencioso. A vítima não faz nada.
- Scope
- Inalterado — impacto limitado ao componente vulnerável.
- Confidentiality
- Alto — perda total de confidencialidade. O atacante pode ler todos os dados.
- Integrity
- Alto — o atacante pode escrever, modificar ou excluir qualquer dado.
- Availability
- Nenhum — sem impacto na disponibilidade.
Software Afetado
Classificação de Fraqueza (CWE)
Linha do tempo
- Reservado
- Publicada
Mitigação e Soluções Alternativastraduzindo…
The recommended mitigation for CVE-2026-1322 is to immediately upgrade GitLab to version 18.11.3 or later. If upgrading is not immediately feasible, consider reviewing and restricting the permissions granted to OAuth applications, specifically limiting the scope of the readapi permission. Implement stricter access controls within GitLab to limit the ability of users to create issues and add comments to private projects. Monitor GitLab audit logs for suspicious activity related to issue creation and comment modification, particularly from OAuth applications. After upgrading, confirm the fix by attempting to create an issue in a private project using a readapi OAuth application; the action should be denied.
Como corrigirtraduzindo…
Actualice GitLab a la versión 18.9.7 o superior, 18.10.6 o superior, o 18.11.3 o superior para mitigar la vulnerabilidad. Esta actualización corrige una falla de autorización que permitía a usuarios autenticados con aplicaciones OAuth crear y comentar en issues de proyectos privados.
Perguntas frequentestraduzindo…
What is CVE-2026-1322 — Authorization Bypass in GitLab?
CVE-2026-1322 is a medium severity vulnerability in GitLab allowing authenticated users with a read_api OAuth application to create issues and comments in private projects, bypassing authorization controls.
Am I affected by CVE-2026-1322 in GitLab?
You are affected if you are running GitLab versions 16.0.0–18.11.3 and have users with read_api scoped OAuth applications.
How do I fix CVE-2026-1322 in GitLab?
Upgrade GitLab to version 18.11.3 or later. As a temporary measure, restrict permissions of OAuth applications and monitor audit logs.
Is CVE-2026-1322 being actively exploited?
There is currently no public evidence of CVE-2026-1322 being actively exploited in the wild.
Where can I find the official GitLab advisory for CVE-2026-1322?
Refer to the official GitLab security advisory for CVE-2026-1322: [https://gitlab.com/security/advisories/CVE-2026-1322](https://gitlab.com/security/advisories/CVE-2026-1322)
Seu projeto está afetado?
Envie seu arquivo de dependências e descubra na hora se esta e outras CVEs te atingem.
Experimente agora — sem conta
Faça upload de qualquer manifesto (composer.lock, package-lock.json, lista de plugins WordPress…) ou cole sua lista de componentes. Receba um relatório de vulnerabilidades instantaneamente. Fazer upload de um arquivo é só o começo: com uma conta, você obtém monitoramento contínuo, alertas por Slack/email, relatórios multiprojeto e white-label.
Arraste e solte seu arquivo de dependências
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...