Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-3160: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.7 before 18.9.7, 18.10 before 18

29
Routine
MEDIUM 5.8REMOTEUPGRADE

CVE-2026-3160 is a medium-severity flaw (CVSS 5.8) affecting gitlab. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.8 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 87%)
CISA exploited listNo
WeaknessCWE-441
Published2026-05-14
Last modified2026-06-17
Publisher (CNA): GitLab Inc. · Vendor: gitlab

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

gitlab gitlab UPGRADE
Affected: >= 13.7.0 and < 18.9.7 · >= 18.10.0 and < 18.10.6 · >= 18.11.0 and < 18.11.3
Fixed in: 18.9.7, 18.10.6, 18.11.3
Safe to downgrade to: a release before 13.7.0
1. Check installed version
apt-cache policy gitlab || rpm -q gitlab || gitlab --version
2. UPGRADE to 18.9.7 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade gitlab
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade gitlab
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 13.7.0 (Debian / Ubuntu)
apt-cache madison gitlab sudo apt install gitlab=<VERSION_BEFORE_13.7.0> sudo apt-mark hold gitlab
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list gitlab sudo dnf downgrade gitlab-<VERSION_BEFORE_13.7.0> sudo dnf versionlock add gitlab
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-3160?

gitlab: upgrade to 18.9.7, 18.10.6, 18.11.3. Exact commands for each OS are on this page.

Is CVE-2026-3160 being exploited?

CVE-2026-3160 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-3160 affect?

CVE-2026-3160 affects gitlab. Severity is medium (CVSS 5.8). 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 s

How urgent is CVE-2026-3160?

Priority 29/100. Remotely exploitable, no login, no user action

Software pages

GitLab vulnerabilities · Atlassian Jira vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.