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-1659: DoS in GitLab 9.0 - 18.11.3
Plateforme
gitlab
Composant
gitlab
Corrigé dans
18.11.3
CVE-2026-1659 describes a denial-of-service vulnerability discovered in GitLab Community Edition (CE) and Enterprise Edition (EE). This flaw allows an unauthenticated attacker to disrupt GitLab services by sending specially crafted requests, leading to resource exhaustion. The vulnerability impacts versions ranging from 9.0.0 through 18.11.3, and a fix is available in version 18.11.3.
Impact et Scénarios d'Attaquetraduction en cours…
Successful exploitation of CVE-2026-1659 can lead to a complete denial of service for GitLab instances. An attacker can overwhelm the server with malicious requests, preventing legitimate users from accessing the platform. This can disrupt critical development workflows, CI/CD pipelines, and collaboration efforts. The lack of authentication required for exploitation significantly broadens the attack surface, as any external user can potentially trigger the DoS. The impact is particularly severe for organizations heavily reliant on GitLab for their software development lifecycle.
Contexte d'Exploitationtraduction en cours…
CVE-2026-1659 was published on May 14, 2026. Severity is currently assessed as HIGH with a CVSS score of 7.5. No public proof-of-concept (POC) code has been released at the time of writing. There are no indications of active exploitation campaigns targeting this vulnerability. Monitor CISA advisories and GitLab security bulletins for updates.
Renseignement sur les Menaces
Statut de l'Exploit
CISA SSVC
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
- Aucun — sans authentification. Aucune identifiant requis pour exploiter.
- 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-1659 is to upgrade GitLab to version 18.11.3 or later. If an immediate upgrade is not feasible, consider implementing rate limiting on incoming requests to the GitLab instance to reduce the impact of potential attacks. Review GitLab's input validation mechanisms and consider implementing stricter controls to prevent malicious data from being processed. Monitor GitLab logs for unusual request patterns that may indicate exploitation attempts. After upgrading, confirm the fix by attempting to trigger the vulnerability with a crafted request; it should now be rejected.
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. Esta actualización aborda la falta de validación de entrada que permitía a usuarios no autenticados causar una denegación de servicio.
Questions fréquentestraduction en cours…
What is CVE-2026-1659 — DoS in GitLab 9.0 - 18.11.3?
CVE-2026-1659 is a denial-of-service vulnerability in GitLab CE/EE allowing unauthenticated users to cause service disruption via crafted requests due to insufficient input validation. It affects versions 9.0.0–18.11.3.
Am I affected by CVE-2026-1659 in GitLab 9.0 - 18.11.3?
If you are running GitLab CE or EE versions 9.0.0 through 18.11.3, you are potentially affected by this vulnerability. Check your GitLab version immediately.
How do I fix CVE-2026-1659 in GitLab 9.0 - 18.11.3?
Upgrade GitLab to version 18.11.3 or later to resolve this vulnerability. Consider rate limiting as a temporary mitigation if an immediate upgrade is not possible.
Is CVE-2026-1659 being actively exploited?
There are currently no indications of active exploitation campaigns targeting CVE-2026-1659, but it's crucial to apply the fix promptly.
Where can I find the official GitLab advisory for CVE-2026-1659?
Refer to the official GitLab security advisory for detailed information and updates: [https://gitlab.com/security/security advisories](https://gitlab.com/security/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...