dbcve.org
GitLabApplication

CVE-2026-1282

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 18.6.6 / 18.7.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an authenticated user to inject malicious content into project labels titles.

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 confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in GitLab CE/EE where an authenticated user can inject malicious JavaScript content into project label titles. The malicious payload persists in the database and executes when other users view the affected labels.

MitigationUpgrade GitLab to version 18.6.6, 18.7.4, 18.8.4 or later. As a temporary mitigation, restrict label creation permissions to trusted users only until the upgrade is completed.

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
Affected:>= 18.6.0, < 18.6.6>= 18.7.0, < 18.7.4>= 18.8.0, < 18.8.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under the Help section to find the exact version number
    Affected if The version falls within 18.6.0 to 18.6.5, 18.7.0 to 18.7.3, or 18.8.0 to 18.8.3
  2. Verify label feature is accessible
    Log in as a standard authenticated user (not admin) and navigate to any project, then go to Issues > Labels to confirm label creation or editing is available
    Affected if Regular authenticated users can create or edit project labels
  3. Inspect database for suspicious label titles
    Connect to the GitLab database and query the labels table: `SELECT id, name, project_id FROM labels WHERE name LIKE '%<script%' OR name LIKE '%javascript:%' OR name LIKE '%onerror%' OR name LIKE '%onload%';`
    Affected if Any labels contain HTML script tags, javascript: protocols, or common XSS event handlers like onerror or onload in their titles
  4. Review audit logs for label creation
    Check GitLab audit logs (Admin Area > Monitoring > Audit Events or via API) filtering for event type 'label' and review recent label creation or update actions for suspicious payloads
    Affected if Audit logs show label titles containing potential XSS patterns

You are affected if your GitLab version is within the affected ranges AND label creation is accessible to authenticated users, or if malicious labels already exist in your database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 18.6.6 / 18.7.4 / 18.8.4 or later
Fixed in 18.6.618.7.418.8.4
Interim mitigation

Upgrade GitLab to version 18.6.6, 18.7.4, 18.8.4 or later. As a temporary mitigation, restrict label creation permissions to trusted users only until the upgrade is completed.

Recommended fix High confidence

18.8.4 (or 18.7.4 or 18.6.6 depending on your branch - 18.8.4 is recommended)

  1. 1. Back up your GitLab instance data and configuration before proceeding with the upgrade.
  2. 2. For GitLab installations using the official omnibus package, run: sudo apt-get update && sudo apt-get install gitlab-ce=<version> (replace <version> with your target version)
  3. 3. Or use sudo gitlab-ctl upgrade to complete the upgrade process
  4. 4. Verify the upgrade was successful by accessing GitLab and checking the version in Help > Version
  5. 5. Confirm the label creation functionality works correctly in a test project

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1282 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1282 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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