Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-9807: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.9 before 18.10.7, 18.11 before 1

17
Routine
MEDIUM 4.3UPGRADE

CVE-2026-9807 is a medium-severity flaw (CVSS 4.3) 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 18.9 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed a blocked Project Access Token to continue accessing private resources due to incorrect authorization enforcement.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score4.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.2% (top 91%)
CISA exploited listNo
WeaknessCWE-863
Published2026-05-28
Last modified2026-10-14
Publisher (CNA): GitLab Inc. · Vendor: gitlab

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

gitlab gitlab UPGRADE
Affected: >= 18.9.0 and < 18.10.7 · >= 18.11.0 and < 18.11.4 · 19.0.0
Fixed in: 18.10.7, 18.11.4
Safe to downgrade to: a release before 18.9.0
1. Check installed version
apt-cache policy gitlab || rpm -q gitlab || gitlab --version
2. UPGRADE to 18.10.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 18.9.0 (Debian / Ubuntu)
apt-cache madison gitlab sudo apt install gitlab=<VERSION_BEFORE_18.9.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_18.9.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-9807?

gitlab: upgrade to 18.10.7, 18.11.4. Exact commands for each OS are on this page.

Is CVE-2026-9807 being exploited?

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

CVE-2026-9807 affects gitlab. Severity is medium (CVSS 4.3). GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.9 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed a blocked Project Access Token to continue accessi

How urgent is CVE-2026-9807?

Priority 17/100. No elevated risk signals yet.

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.