CVE-2026-7250
GitLab Analyse et atténuation des vulnérabilités

Aperçu

CVE-2026-7250 is a denial-of-service vulnerability in GitLab CE/EE caused by improper input validation in the API request parsing middleware. It affects all versions from 12.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. The vulnerability was disclosed on June 11, 2026, and has a CVSS v3.1 base score of 7.5 (High) (GitHub Advisory, GitLab Patch Release).

Détails techniques

The root cause is classified as CWE-770 (Allocation of Resources Without Limits or Throttling), meaning the API request parsing middleware fails to impose adequate restrictions on resource allocation when processing certain malformed or oversized inputs. An unauthenticated remote attacker can craft malicious API requests that trigger excessive resource consumption in the middleware layer, causing the GitLab service to become unavailable. No authentication, user interaction, or special privileges are required to exploit this vulnerability, and it is exploitable over the network with low attack complexity (GitHub Advisory).

Impact

Successful exploitation results in a denial-of-service condition, rendering the GitLab instance unavailable to legitimate users. The impact is limited to availability — there is no confidentiality or integrity impact, meaning attackers cannot access or modify data through this vulnerability alone. However, disruption of a GitLab instance could halt CI/CD pipelines, block code commits, and impair development workflows for all users of the affected instance (GitHub Advisory).

Atténuation et solutions de contournement

GitLab has released patched versions addressing this vulnerability: 18.10.8, 18.11.5, and 19.0.2. Administrators should upgrade to the appropriate fixed version based on their current deployment. No configuration-based workaround has been published; upgrading is the recommended and only confirmed remediation (GitLab Patch Release, GitHub Advisory).

Réactions de la communauté

Security news outlets including GBHackers and CyberPress covered the patch release as part of GitLab's broader June 2026 security update, noting multiple vulnerabilities addressed simultaneously (GBHackers, CyberPress). SecurityOnline.info also reported on the GitLab 19.0.2 security updates shortly after disclosure. Coverage generally characterized the vulnerability as high severity due to its unauthenticated network exploitability, though no significant researcher commentary or threat actor attribution has emerged.

Ressources additionnelles


SourceCe rapport a été généré à l’aide de l’IA

Apparenté GitLab Vulnérabilités:

Identifiant CVE

Sévérité

Score

Technologies

Nom du composant

Exploit CISA KEV

A corrigé

Date de publication

CVE-2026-8589HIGH8.7
  • GitLabGitLab
  • gitlab-cng-19.0
NonOuiJun 11, 2026
CVE-2026-7250HIGH7.5
  • GitLabGitLab
  • gitlab-cng-fips-19.0
NonOuiJun 11, 2026
CVE-2026-9204MEDIUM6.5
  • GitLabGitLab
  • gitlab
NonOuiJun 11, 2026
CVE-2026-9694MEDIUM4.3
  • GitLabGitLab
  • gitlab-cng-fips-19.0
NonOuiJun 11, 2026
CVE-2026-6976LOW3.7
  • GitLabGitLab
  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
NonOuiJun 11, 2026

Évaluation gratuite des vulnérabilités

Évaluez votre posture de sécurité dans le cloud

Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité pour évaluer votre niveau de risque et identifier les failles dans vos défenses.

Demander une évaluation

Obtenez une démo personnalisée

Prêt(e) à voir Wiz en action ?

"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
David EstlickRSSI
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
Adam FletcherChef du service de sécurité
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."
Greg PoniatowskiResponsable de la gestion des menaces et des vulnérabilités