GitLabApplication
CVE-2025-9222
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGitLab 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAuthenticated users could achieve stored cross-site scripting by exploiting GitLab Flavored Markdown rendering, allowing injection of malicious scripts that execute when other users view the crafted Markdown content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitLabApplication
>= 18.2.2, < 18.5.5>= 18.6.0, < 18.6.3= 18.7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed GitLab versionLog into the GitLab admin area and navigate to the Admin Overview > Dashboard, or run `gitlab-rake gitlab:env:info` from the server CLI to retrieve the exact version numberAffected if The version matches >= 18.2.2 and < 18.5.5, OR >= 18.6.0 and < 18.6.3, OR exactly 18.7.0
-
Verify GitLab Flavored Markdown is in useConfirm that GitLab instances have Markdown rendering enabled for issues, merge requests, comments, or wikis. This is enabled by default in GitLab. Check via Admin Area > Settings > Markdown or review .md file rendering in any projectAffected if Markdown rendering is active, which is the default state for all standard GitLab installations
-
Audit recent markdown content creationSearch GitLab audit logs for recent activity involving markdown content in issues, merge requests, comments, or wikis using Admin Area > Audit Events, filtering by event type for content creationAffected if Malicious crafted markdown with script injection was created by an authenticated user and persists in the system
A GitLab instance is affected if its installed version falls within the specified vulnerable ranges and Markdown rendering is enabled, which is the default configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped18.5.518.6.3
Upgrade GitLab to version 18.5.5, 18.6.3, 18.7.1 or later to apply the patch.
18.5.5, 18.6.3, or 18.7.1 (minimum 18.5.5, recommended 18.7.1 or later)
- Identify your current GitLab version using `sudo gitlab-rake gitlab:version`
- Review the GitLab upgrade documentation for your current version to 18.5.5, 18.6.3, or 18.7.1+
- Create a full backup of your GitLab instance using `sudo gitlab-backup-create`
- Ensure you have adequate downtime window as recommended by GitLab upgrade documentation
- For package installations (Omnibus), run: `sudo apt-get update && sudo apt-get install gitlab-ee` (or `gitlab-ce`)
- For source installations, follow the GitLab upgrade path documentation to upgrade to the target version
- After upgrade, verify the instance is operational: `sudo gitlab-rake gitlab:check`
- Confirm the new version: `sudo gitlab-rake gitlab:version`
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9222 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9222 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data