Is CVE-2025-9222 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-9222 being exploited in the wild.

How severe is CVE-2025-9222?

High severity, with a CVSS score of 8.7, published 9 January 2026.

Which products and versions are affected?

GitLab Community Edition 18.2.2 to 18.5.4, 18.6.0 to 18.6.2, 18.7.0; GitLab Enterprise Edition 18.2.2 to 18.5.4, 18.6.0 to 18.6.2, 18.7.0.

Is there a fix for CVE-2025-9222?

A patch was published on 2026-01-07: GitLab released versions 18.7.1, 18.6.3, and 18.5.5 containing the fix. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-9222 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2025-9222?

Check whether you run GitLab Community Edition or GitLab Enterprise Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-9222: GitLab CE/EE stored XSS in GitLab Flavored Markdown placeholders

CVE-2025-9222 · Severity: high · CVSS 8.7 · Published 2026-01-09

GitLab has fixed a high-severity security flaw in its Community and Enterprise editions that could allow a logged-in user to execute malicious scripts in the browsers of other users. This occurs when the platform processes specially formatted text (Markdown) used in comments, issues, or descriptions. If exploited, an attacker could potentially steal session information or perform unauthorized actions on behalf of other users, including administrators.

Technologies: GitLab Community Edition, GitLab Enterprise Edition. Vendors: GitLab.

Quick answers

Is CVE-2025-9222 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-9222 being exploited in the wild.
How severe is CVE-2025-9222?: High severity, with a CVSS score of 8.7, published 9 January 2026.
Which products and versions are affected?: GitLab Community Edition 18.2.2 to 18.5.4, 18.6.0 to 18.6.2, 18.7.0; GitLab Enterprise Edition 18.2.2 to 18.5.4, 18.6.0 to 18.6.2, 18.7.0.
Is there a fix for CVE-2025-9222?: A patch was published on 2026-01-07: GitLab released versions 18.7.1, 18.6.3, and 18.5.5 containing the fix. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-9222 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2025-9222?: Check whether you run GitLab Community Edition or GitLab Enterprise Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A stored cross-site scripting (XSS) vulnerability exists in GitLab CE/EE due to improper neutralization of input during the processing of GitLab Flavored Markdown (GLFM) placeholders. An authenticated attacker can exploit this by injecting malicious scripts into Markdown-enabled fields (such as issue descriptions or comments). When other users view the affected content, the script executes in their browser context. This vulnerability is assigned a CVSS score of 8.7 because it allows for a scope change (S:C), potentially leading to full compromise of the victim's session. The issue is fixed in versions 18.5.5, 18.6.3, and 18.7.1.

Affected products

GitLab GitLab Community Edition (CE) 18.2.2 to 18.5.4, 18.6.0 to 18.6.2, 18.7.0
GitLab GitLab Enterprise Edition (EE) 18.2.2 to 18.5.4, 18.6.0 to 18.6.2, 18.7.0

Timeline

2026-01-07: patched: GitLab released versions 18.7.1, 18.6.3, and 18.5.5 containing the fix.
2026-01-09: disclosed: Public disclosure of CVE-2025-9222.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.