dbcve.org
GitLabApplication

CVE-2026-3160

MEDIUM · 5.8 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 →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 13.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to view Jira issues outside the configured project scope due to an integration filter functioning only as a display control rather than enforcing access boundaries as specified.

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

GitLab's Jira integration filter only controlled UI display rather than enforcing access boundaries, allowing authenticated users to view Jira issues from projects outside their authorized scope. This authorization bypass occurred because the integration filter functioned as a display control instead of properly scoping API queries to permitted projects.

MitigationUpgrade GitLab to versions 18.9.7, 18.10.6, 18.11.3 or later. After upgrading, verify that Jira issue visibility is correctly restricted to the configured project scope.

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:>= 13.7.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
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version to find the exact version number
    Affected if The installed version falls within any of these ranges: >= 13.7.0 and < 18.9.7, OR >= 18.10.0 and < 18.10.6, OR >= 18.11.0 and < 18.11.3
  2. Verify Jira integration is configured
    Navigate to Admin Area > Applications > Jira or go to Project Settings > Integrations > Jira to confirm Jira integration is enabled
    Affected if Jira integration is active and connected to external Jira instances
  3. Confirm project filter scope settings
    In the Jira integration settings, locate any project filter, scope, or visibility configuration that limits which projects can access Jira issues
    Affected if A filter or scope is configured but relies on UI display controls rather than enforced API boundaries
  4. Test cross-project issue access
    As an authenticated user with access to one project that has Jira integration, attempt to access Jira issues from a different project that the user should not have access to via the integrated Jira links
    Affected if User can view Jira issues from projects outside their authorized scope through the integration

Your environment is affected if the installed GitLab version is within the affected ranges AND Jira integration is enabled with project filters that only control UI display rather than enforcing proper access boundaries.

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 versions 18.9.7, 18.10.6, 18.11.3 or later. After upgrading, verify that Jira issue visibility is correctly restricted to the configured project scope.

Recommended fix High confidence

18.9.7, 18.10.6, or 18.11.3 (preferably 18.11.3 as the latest stable fixed release)

  1. Back up your GitLab instance database and repositories before starting the upgrade
  2. Update your GitLab package repository to fetch the latest available packages
  3. Run the appropriate package upgrade command for your installation method (e.g., `sudo apt-get update && sudo apt-get install gitlab-ee` for Debian/Ubuntu, or `sudo yum install gitlab-ee` for RHEL/CentOS)
  4. After installation, run `sudo gitlab-ctl reconfigure` to apply the configuration
  5. Verify the GitLab version matches the expected fixed release (18.9.7, 18.10.6, or 18.11.3) using `sudo gitlab-rake gitlab:env:info`
  6. Test the Jira integration to confirm issues are properly scoped to the configured project boundaries
Caveat Review GitLab release notes for any breaking changes between your current version and the target version before upgrading

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
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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