Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-75871: GitLab has remediated a vulnerability in the GitLab AI Gateway component affecting all versions of the AI Gate

35
Routine
HIGH 8.2UPGRADE

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

GitLab has remediated a vulnerability in the GitLab AI Gateway component affecting all versions of the AI Gateway from 18.10 to 19.0.12, 19.1 to 19.1.7, and 19.2 to 19.2.2 that could have allowed an authenticated user with Duo Agent Platform access to redirect outbound model requests to an externally-controlled endpoint via a crafted inline flow configuration that overrides the HTTP Host header, resulting in disclosure of Google Cloud Vertex clou

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.2 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededLow
User interactionNone
EPSS exploit chance0.3% (top 73%)
CISA exploited listNo
WeaknessCWE-918
Published2026-08-27
Last modified2026-09-01
Publisher (CNA): GitLab Inc. · Vendor: gitlab

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

gitlab gitlab UPGRADE
Affected: >= 18.10.0 and < 19.0.12 · >= 19.1.0 and < 19.1.7 · >= 19.2.0 and < 19.2.2
Fixed in: 19.0.12, 19.1.7, 19.2.2
Safe to downgrade to: a release before 18.10.0
1. Check installed version
apt-cache policy gitlab || rpm -q gitlab || gitlab --version
2. UPGRADE to 19.0.12 (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.10.0 (Debian / Ubuntu)
apt-cache madison gitlab sudo apt install gitlab=<VERSION_BEFORE_18.10.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.10.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-75871?

gitlab: upgrade to 19.0.12, 19.1.7, 19.2.2. Exact commands for each OS are on this page.

Is CVE-2026-75871 being exploited?

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

CVE-2026-75871 affects gitlab. Severity is high (CVSS 8.2). GitLab has remediated a vulnerability in the GitLab AI Gateway component affecting all versions of the AI Gateway from 18.10 to 19.0.12, 19.1 to 19.1.7, and 19.2 to 19.2.2 that could have allowed an authenticated user with Duo Agent Platfor

How urgent is CVE-2026-75871?

Priority 35/100. High severity

Software pages

GitLab vulnerabilities · Google Cloud 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.