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-7481: XSS in GitLab 16.4 - 18.11.3
Plateforme
gitlab
Composant
gitlab
Corrigé dans
18.11.3
CVE-2026-7481 describes a Cross-Site Scripting (XSS) vulnerability discovered in GitLab EE. This flaw allows an authenticated user possessing developer-role permissions to inject and execute arbitrary JavaScript code within the browsers of other GitLab users. The vulnerability impacts versions ranging from 16.4.0 through 18.11.3, and a patch is available in version 18.11.3.
Impact et Scénarios d'Attaquetraduction en cours…
Successful exploitation of CVE-2026-7481 could lead to a wide range of malicious activities. An attacker could steal session cookies, allowing them to impersonate other users and gain unauthorized access to sensitive data and functionality. They could also deface GitLab pages, redirect users to phishing sites, or inject malware. The impact is particularly severe because the vulnerability requires only developer-role permissions, a relatively common role within GitLab environments, expanding the potential attack surface significantly. This vulnerability shares similarities with other XSS vulnerabilities where user input is not properly sanitized before being rendered in a web page.
Contexte d'Exploitationtraduction en cours…
CVE-2026-7481 was published on 2026-05-14. Its severity is rated HIGH with a CVSS score of 8.7. There are currently no publicly known Proof-of-Concept (POC) exploits available. The vulnerability is not listed on KEV or EPSS, suggesting a low to medium probability of active exploitation at this time. Monitor security advisories and threat intelligence feeds for any updates regarding exploitation attempts.
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
- Faible — tout compte utilisateur valide est suffisant.
- User Interaction
- Requise — la victime doit ouvrir un fichier, cliquer sur un lien ou visiter une page.
- Scope
- Modifié — l'attaque peut pivoter au-delà du composant vulnérable.
- Confidentiality
- Élevé — perte totale de confidentialité. L'attaquant peut lire toutes les données.
- Integrity
- Élevé — l'attaquant peut écrire, modifier ou supprimer toutes les données.
- Availability
- Aucun — aucun impact sur la disponibilité.
Logiciel Affecté
Classification de Faiblesse (CWE)
Chronologie
- Réservé
- Publiée
Mitigation et Contournementstraduction en cours…
The primary mitigation for CVE-2026-7481 is to upgrade GitLab EE to version 18.11.3 or later. If an immediate upgrade is not feasible, consider implementing stricter input validation and output encoding within your GitLab instance. While not a complete solution, a Web Application Firewall (WAF) configured to detect and block XSS payloads can provide an additional layer of defense. Regularly review and update GitLab's security configuration to minimize the risk of similar vulnerabilities. After upgrading, confirm the fix by attempting to trigger the XSS vulnerability with a known payload and verifying that it is no longer successful.
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 Cross-Site Scripting (XSS). Esta actualización corrige la falta de sanitización adecuada de la entrada, previniendo la ejecución de código JavaScript malicioso en el navegador de otros usuarios.
Questions fréquentestraduction en cours…
What is CVE-2026-7481 — XSS in GitLab?
CVE-2026-7481 is a Cross-Site Scripting (XSS) vulnerability in GitLab EE that allows authenticated users with developer role to execute JavaScript in other users' browsers due to improper input sanitization.
Am I affected by CVE-2026-7481 in GitLab?
You are affected if you are running GitLab EE versions 16.4.0 through 18.11.3. Upgrade to version 18.11.3 or later to mitigate the risk.
How do I fix CVE-2026-7481 in GitLab?
The recommended fix is to upgrade GitLab EE to version 18.11.3 or a later version. Consider implementing WAF rules as an interim measure.
Is CVE-2026-7481 being actively exploited?
Currently, there are no publicly known active exploitation campaigns for CVE-2026-7481, but continuous monitoring is advised.
Where can I find the official GitLab advisory for CVE-2026-7481?
Refer to the official GitLab security advisory for CVE-2026-7481 on the GitLab website: [https://about.gitlab.com/security/advisories/](https://about.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...