GitLabApplication
CVE-2026-6896
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 EE affecting all versions from 13.11 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary scripts in another user's browser session due to improper sanitization of user-supplied input.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 confidenceA stored cross-site scripting (XSS) vulnerability in GitLab EE allows authenticated users with developer-role permissions to inject malicious scripts through unsanitized user-supplied input, which then executes in other users' browser sessions when they view the affected 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
>= 13.11.0, < 18.11.7>= 19.0.0, < 19.0.4>= 19.1.0, < 19.1.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
- 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 versionAccess the GitLab Admin area > Dashboard or run `gitlab-rake gitlab:env:info` to view the installed version. Alternatively, check the version file in the GitLab installation directory.Affected if The installed version falls within any of these ranges: 13.11.0 to 18.11.6, 19.0.0 to 19.0.3, or 19.1.0 to 19.1.1
-
Identify developer-role usersIn the GitLab Admin area, navigate to Users and filter or search for users with Developer role permissions. Alternatively, use the API or `gitlab-rake gitlab:ldap:check` if LDAP integration exists.Affected if Any users with Developer role or higher permissions exist in the system
-
Locate user-supplied input fieldsReview GitLab projects, issues, merge requests, snippets, wiki pages, or other features where authenticated users can submit content. Focus on fields that accept free-form text input.Affected if User-supplied input fields exist that could accept and store content without sanitization
-
Review recent user-created contentInspect recent issues, merge requests, comments, snippets, and wiki edits created by Developer-role users for unexpected script tags or HTML attributes.Affected if Content containing unsanitized script tags, event handlers, or HTML injection vectors is present in the database
The environment is affected if GitLab version is below 18.11.7, 19.0.4, or 19.1.2 AND Developer-role users can submit content to fields that are not properly sanitized.
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.11.719.0.419.1.2
Upgrade GitLab to version 18.11.7, 19.0.4, or 19.1.2 or later. No configuration-based workarounds exist; patching is the only remediation path.
18.11.7 (or 19.1.2 for latest stable)
- Identify your current GitLab version using the GitLab Rails console (gitlab-rake gitlab:env:info) or the Admin Area UI
- Backup your GitLab instance before upgrading
- Schedule a maintenance window for the upgrade
- Upgrade to GitLab 18.11.7 or later for the 18.x branch, 19.0.4 or later for the 19.0.x branch, or 19.1.2 or later for the 19.1.x branch
- After upgrade, verify the instance is running correctly and test that the XSS fix is applied
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 / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6896 — 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-2026-6896 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