GitLabApplication
CVE-2025-8405
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 a security issue in GitLab CE/EE affecting all versions from 17.1 before 18.4.6, 18.5 before 18.5.4, and 18.6 before 18.6.2 that could have allowed an authenticated user to perform unauthorized actions on behalf of other users by injecting malicious HTML into vulnerability code flow displays.
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 confidenceThis is an HTML injection vulnerability in GitLab's vulnerability code flow display feature that allows authenticated users to inject malicious HTML, potentially enabling unauthorized actions on behalf of other users (similar to a stored XSS with CSRF-like impact).
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
>= 17.1.0, < 18.4.6>= 18.5.0, < 18.5.4>= 18.6.0, < 18.6.2CVSS 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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/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 versionRun `sudo gitlab-rake gitlab:version` or check the GitLab admin dashboard under Help > Version to find the exact version numberAffected if The version falls within >= 17.1.0 and < 18.4.6, OR >= 18.5.0 and < 18.5.4, OR >= 18.6.0 and < 18.6.2
-
Verify vulnerability code flow feature is accessibleNavigate to a project with security scanning enabled, then go to Security > Vulnerabilities and check if the code flow display (showing vulnerability details with code snippets) is available to authenticated usersAffected if The vulnerability code flow feature is enabled and accessible to at least some authenticated users in the instance
-
Check for existing vulnerability reportsGo to Project > Security > Vulnerabilities in any project with GitLab security scanning (SAST, DAST, dependency scanning, etc.) enabled and look for any vulnerability entries that display code contextAffected if There are existing vulnerability reports with code flow display accessible to authenticated users
The environment is affected if the installed GitLab version is within any of the affected ranges AND the vulnerability code flow feature is accessible to authenticated users on the instance.
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.4.618.5.418.6.2
Upgrade GitLab to version 18.4.6, 18.5.4, or 18.6.2 or later. For self-hosted deployments, plan and execute the upgrade following GitLab's upgrade path documentation, ensuring backup and staging validation.
18.4.6 (for 17.x users) / 18.5.4 (for 18.5.x users) / 18.6.2 (for 18.6.x users)
- Identify your current GitLab version using the GitLab Rails console or admin panel
- Determine which version range you fall into: 17.1.0-17.x, 18.5.0-18.5.x, or 18.6.0-18.6.1
- Backup your GitLab instance database and repositories before upgrading
- For 17.x branches: upgrade to GitLab 18.4.6 or later
- For 18.5.x branches: upgrade to GitLab 18.5.4 or later
- For 18.6.x branches: upgrade to GitLab 18.6.2 or later
- After upgrade, verify the vulnerability is remediated by testing HTML injection in vulnerability reports
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8405 — 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-8405 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