このページはまだあなたの言語に翻訳されていません。翻訳作業中のため、英語でコンテンツを表示しています。
💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.
CVE-2026-6073: XSS in GitLab 18.7 - 18.11
プラットフォーム
gitlab
コンポーネント
gitlab
修正版
18.11.3
CVE-2026-6073 describes a Cross-Site Scripting (XSS) vulnerability discovered in GitLab EE. This flaw allows an authenticated user to inject and execute arbitrary JavaScript code within the browsers of other GitLab users. The vulnerability impacts versions 18.7.0 through 18.11.3, and a patch is available in version 18.11.3.
影響と攻撃シナリオ翻訳中…
Successful exploitation of CVE-2026-6073 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. They could also inject malicious scripts to deface GitLab pages, redirect users to phishing sites, or even execute arbitrary commands on the server if the browser has sufficient privileges. The impact is particularly severe given GitLab's widespread use in software development and DevOps workflows, where sensitive code and project data are often stored.
悪用の状況翻訳中…
CVE-2026-6073 was published on May 14, 2026. As of this date, there is no public evidence of active exploitation in the wild. The vulnerability is not currently listed on KEV or EPSS, suggesting a low to medium probability of exploitation. Public proof-of-concept (POC) code may emerge, increasing the risk. Refer to the official GitLab advisory for further details.
脅威インテリジェンス
エクスプロイト状況
CVSS ベクトル
これらのメトリクスの意味は？
- Attack Vector
- ネットワーク — インターネット経由でリモートから悪用可能。物理・ローカルアクセス不要。
- Attack Complexity
- 低 — 特別な条件不要。安定して悪用可能。
- Privileges Required
- 低 — 有効なユーザーアカウントがあれば十分。
- User Interaction
- 必要 — 被害者がファイルを開く、リンクをクリックするなどのアクションが必要。
- Scope
- 変化あり — 攻撃が脆弱なコンポーネントを超えて他のシステムに波及可能。
- Confidentiality
- 高 — 機密性の完全喪失。全データが読み取り可能。
- Integrity
- 高 — 任意のデータの書き込み・変更・削除が可能。
- Availability
- なし — 可用性への影響なし。
影響を受けるソフトウェア
弱点分類 (CWE)
タイムライン
- 予約済み
- 公開日
緩和策と回避策翻訳中…
The primary mitigation for CVE-2026-6073 is to upgrade GitLab EE to version 18.11.3 or later. If an immediate upgrade is not possible, consider implementing stricter input validation and output encoding measures to sanitize user-supplied data. Web Application Firewalls (WAFs) configured with rules to detect and block XSS payloads can provide an additional layer of defense. Regularly review and update GitLab's security configuration to ensure best practices are followed. After upgrading, confirm the fix by attempting to inject a simple JavaScript payload through a user input field and verifying that it is properly sanitized.
修正方法翻訳中…
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 del usuario, previniendo la ejecución de código JavaScript malicioso en el navegador de otros usuarios. Consulte las notas de la versión para obtener instrucciones detalladas de actualización.
よくある質問翻訳中…
What is CVE-2026-6073 — XSS in GitLab?
CVE-2026-6073 is a Cross-Site Scripting (XSS) vulnerability in GitLab EE that allows authenticated users to execute JavaScript in other users' browsers. It affects versions 18.7.0–18.11.3.
Am I affected by CVE-2026-6073 in GitLab?
You are affected if you are running GitLab EE versions 18.7.0 through 18.11.3. Check your GitLab version immediately and upgrade if necessary.
How do I fix CVE-2026-6073 in GitLab?
Upgrade GitLab EE to version 18.11.3 or later. If immediate upgrade isn't possible, implement stricter input validation and output encoding.
Is CVE-2026-6073 being actively exploited?
As of May 14, 2026, there is no public evidence of active exploitation in the wild, but the risk remains until patched.
Where can I find the official GitLab advisory for CVE-2026-6073?
Refer to the official GitLab security advisory for CVE-2026-6073: [https://gitlab.com/security/advisories/CVE-2026-6073](https://gitlab.com/security/advisories/CVE-2026-6073)
今すぐ試す — アカウント不要
Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
依存関係ファイルをドラッグ＆ドロップ
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...