dbcve.org
GitLabApplication

CVE-2026-4527

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-14
Fix available
A fix is available. Upgrade to 18.9.7 / 18.10.6 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 11.10 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an unauthenticated user to create unauthorized Jira subscriptions for a targeted user's namespace via a specially crafted link due to missing CSRF protection.

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 CSRF (Cross-Site Request Forgery) vulnerability in GitLab's Jira integration. An unauthenticated attacker can craft a malicious link that, when clicked by a targeted authenticated user, will create unauthorized Jira subscriptions in that user's namespace without their consent. The root cause is missing CSRF protection on the Jira subscription creation endpoints.

MitigationUpgrade GitLab to version 18.9.7, 18.10.6, 18.11.3 or later. These versions include proper CSRF token validation on Jira subscription endpoints to prevent unauthorized subscription creation.

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:>= 11.10.0, < 18.9.7>= 18.10.0, < 18.10.6>= 18.11.0, < 18.11.3

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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
    Retrieve the GitLab version from the instance using the Admin area UI, API endpoint /api/v4/version, or the gitlab-rake gitlab:env:info command
    Affected if The installed version falls within any of these ranges: 11.10.0 to 18.9.6, 18.10.0 to 18.10.5, or 18.11.0 to 18.11.2
  2. Check if Jira integration is enabled
    Navigate to the GitLab Admin area under Integrations or check via API at /api/v4/integrations to see if Jira integration is active for the instance or any group/project
    Affected if Jira integration is enabled and configured for any namespace in the GitLab instance
  3. Verify CSRF protection on Jira subscription endpoints
    Inspect the GitLab Rails application code or attempt a test subscription creation request to verify whether the /api/v4/integrations/jira_subscriptions endpoint requires and validates a CSRF token
    Affected if The endpoint accepts POST requests without proper CSRF token validation (no token required or token not validated)

A user is affected if their GitLab version is 11.10.0 through 18.9.6, 18.10.0 through 18.10.5, or 18.11.0 through 18.11.2 AND the Jira integration feature is enabled or configured.

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.9.7 / 18.10.6 / 18.11.3 or later
Fixed in 18.9.718.10.618.11.3
Interim mitigation

Upgrade GitLab to version 18.9.7, 18.10.6, 18.11.3 or later. These versions include proper CSRF token validation on Jira subscription endpoints to prevent unauthorized subscription creation.

Recommended fix High confidence

Upgrade to GitLab 18.9.7, 18.10.6, 18.11.3, or later (recommended: latest stable 18.x release)

  1. 1. Backup your GitLab instance data and configuration before proceeding with the upgrade.
  2. 2. Review the GitLab upgrade documentation for your current installation method (Omnibus, source, etc.).
  3. 3. Plan for maintenance window as GitLab upgrade may require downtime.
  4. 4. For Omnibus installations: Update your package repository and install the appropriate version (18.9.7, 18.10.6, or 18.11.3 or later).
  5. 5. For source installations: Clone the specific tagged release (e.g., v18.11.3) and follow the upgrade documentation.
  6. 6. Run 'gitlab-ctl reconfigure' after package installation for Omnibus deployments.
  7. 7. Verify the upgrade by logging in and checking GitLab version information.
  8. 8. Test that Jira integrations are functioning correctly post-upgrade.
Caveat Major version upgrades may include breaking changes; review GitLab upgrade guides and release notes before upgrading across multiple minor versions

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4527 — 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-4527 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