Cette page n'a pas encore été traduite dans votre langue. Affichage du contenu en anglais pendant que nous y travaillons.
💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.
CVE-2026-1184: Insecure Deserialization in GitLab
Plateforme
gitlab
Composant
gitlab
Corrigé dans
18.11.3
CVE-2026-1184 addresses an Insecure Deserialization vulnerability discovered in GitLab EE. This flaw allows an unauthenticated user to induce a denial of service (DoS) by uploading a specially crafted file. The vulnerability impacts GitLab EE versions ranging from 11.9.0 through 18.11.3, and is resolved in version 18.11.3.
Impact et Scénarios d'Attaquetraduction en cours…
Successful exploitation of CVE-2026-1184 allows an attacker to disrupt GitLab services, rendering them unavailable to legitimate users. The attacker does not require authentication, significantly broadening the potential attack surface. The denial of service can manifest as system instability, performance degradation, or complete service outage. While the vulnerability doesn't directly lead to data exfiltration or code execution, the disruption of GitLab services can severely impact development workflows and project timelines. The impact is amplified in environments where GitLab is a critical component of the software development lifecycle.
Contexte d'Exploitationtraduction en cours…
CVE-2026-1184 was published on 2026-05-14. Its severity is currently assessed as Medium (CVSS 6.5). No public proof-of-concept (POC) code has been publicly released as of this writing. There are no indications of active exploitation campaigns targeting this vulnerability. The vulnerability is not currently listed on CISA Known Exploited Vulnerabilities (KEV) catalog.
Renseignement sur les Menaces
Statut de l'Exploit
Vecteur CVSS
Que signifient ces métriques?
- Attack Vector
- Réseau — exploitable à distance via internet. Aucun accès physique ou local requis.
- Attack Complexity
- Faible — aucune condition spéciale requise. Exploitable de manière fiable.
- Privileges Required
- Faible — tout compte utilisateur valide est suffisant.
- User Interaction
- Aucune — attaque automatique et silencieuse. La victime ne fait rien.
- Scope
- Inchangé — impact limité au composant vulnérable.
- Confidentiality
- Aucun — aucun impact sur la confidentialité.
- Integrity
- Aucun — aucun impact sur l'intégrité.
- Availability
- Élevé — panne complète ou épuisement des ressources. Déni de service total.
Logiciel Affecté
Classification de Faiblesse (CWE)
Chronologie
- Réservé
- Publiée
Mitigation et Contournementstraduction en cours…
The primary mitigation for CVE-2026-1184 is to upgrade GitLab EE to version 18.11.3 or later. If immediate upgrade is not feasible, consider implementing temporary workarounds such as restricting file uploads from unauthenticated users or implementing stricter file validation rules. Review GitLab's file upload policies and ensure they are enforced. Monitor GitLab logs for suspicious file upload activity. After upgrading, verify the fix by attempting a file upload with a known malicious payload (in a controlled environment) to confirm the vulnerability is no longer exploitable.
Comment corrigertraduction en cours…
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 de deserialización de datos no confiables. Esta actualización corrige la validación incorrecta de archivos cargados, previniendo posibles ataques de denegación de servicio.
Questions fréquentestraduction en cours…
What is CVE-2026-1184 — Insecure Deserialization in GitLab?
CVE-2026-1184 is a Medium severity vulnerability in GitLab EE allowing unauthenticated users to trigger a denial of service by uploading a crafted file due to improper validation. It affects versions 11.9.0–18.11.3.
Am I affected by CVE-2026-1184 in GitLab?
You are affected if you are running GitLab EE versions 11.9.0 through 18.11.3. Versions prior to 18.11.3 are vulnerable to denial of service attacks.
How do I fix CVE-2026-1184 in GitLab?
Upgrade GitLab EE to version 18.11.3 or later to resolve the vulnerability. Consider temporary workarounds like restricting unauthenticated file uploads if immediate upgrade is not possible.
Is CVE-2026-1184 being actively exploited?
As of the current assessment, there are no indications of active exploitation campaigns targeting CVE-2026-1184.
Where can I find the official GitLab advisory for CVE-2026-1184?
Refer to the official GitLab security advisory for CVE-2026-1184 on the GitLab website: [https://gitlab.com/security/advisories/](https://gitlab.com/security/advisories/)
Ton projet est-il affecté ?
Téléverse ton fichier de dépendances et découvre instantanément si cette CVE et d'autres te touchent.
Essayez maintenant — sans compte
scanZone.subtitle
Glissez-déposez votre fichier de dépendances
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...