Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-9222 high CVSS 8.7

Cross-Site Scripting (XSS) in gitlab (CVE-2025-9222)

Summary

Cross-site scripting in gitlab (CVE-2025-9222). Confidential information can be exposed externally. Mitigation: upgrade to 18.5.5, 18.6.3, 18.7.1 or later.

Original description

The description as published by the source.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2.2 before 18.5.5, 18.6 before 18.6.3, and 18.7 before 18.7.1 that could have allowed an authenticated user to achieve stored cross-site scripting by exploiting GitLab Flavored Markdown.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-9222 has been found in gitlab.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade gitlab to 18.5.5, 18.6.3, 18.7.1 or later.
If unsure, ask your IT team or search "gitlab CVE-2025-9222" on the vendor's site.

CVE-2025-9222 (gitlab) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Patched: 18.5.5, 18.6.3, 18.7.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in gitlab.

📍 Affected scope

Check the vendor advisory for the affected versions of gitlab.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 18.5.5, 18.6.3, 18.7.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gitlab' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'gitlab' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で gitlab を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade gitlab to 18.5.5, 18.6.3, 18.7.1

    ステージング環境で 18.5.5, 18.6.3, 18.7.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami gitlab
[{"type":"SEMVER","events":[{"introduced":"18.2.2"},{"fixed":"18.5.5"},{"introduced":"18.6.0"},{"fixed":"18.6.3"},{"introduced":"18.7.0"},{"fixed":"18.7.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details