Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-10087: GitLab has remediated an issue in GitLab EE affecting all versions from 17.1 before 18.10.8, 18.11 before 18.1

36
Routine
HIGH 8.7UPGRADE

CVE-2026-10087 is a high-severity flaw (CVSS 8.7) 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 EE affecting all versions from 17.1 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary client-side code on behalf of a targeted user due to improper input sanitization in the Analytics Dashboard.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.7 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionRequired
EPSS exploit chance0.3% (top 76%)
CISA exploited listNo
WeaknessCWE-79
Published2026-06-11
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: >= 17.1.0 and < 18.10.8 · >= 18.11.0 and < 18.11.5 · >= 19.0.0 and < 19.0.2
Fixed in: 18.10.8, 18.11.5, 19.0.2
Safe to downgrade to: a release before 17.1.0
1. Check installed version
apt-cache policy gitlab || rpm -q gitlab || gitlab --version
2. UPGRADE to 18.10.8 (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 17.1.0 (Debian / Ubuntu)
apt-cache madison gitlab sudo apt install gitlab=<VERSION_BEFORE_17.1.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_17.1.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.

Advisories and coverage

Official advisories

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-10087?

gitlab: upgrade to 18.10.8, 18.11.5, 19.0.2. Exact commands for each OS are on this page.

Is CVE-2026-10087 being exploited?

CVE-2026-10087 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-10087 affect?

CVE-2026-10087 affects gitlab. Severity is high (CVSS 8.7). GitLab has remediated an issue in GitLab EE affecting all versions from 17.1 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with developer-role permissions

How urgent is CVE-2026-10087?

Priority 36/100. High severity

Software pages

GitLab 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.