CVE-2026-75871: 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...
Critical CVSS 9.6
- CVE id
- CVE-2026-75871
- Published
- Last modified
Affected packages
How to fix it
GitLab CE (Runtimes and servers)
Upgrade GitLab CE to the fixed release of the line you run: 19.0.12, 19.1.7, 19.2.2.
gitlab-rake gitlab:env:info
- Upgrade your self-managed GitLab (the gitlab/gitlab-ce image tag or the gitlab-ce package) to the patched release of your series.
GitLab EE (Runtimes and servers)
Upgrade GitLab EE to the fixed release of the line you run: 19.0.12, 19.1.7, 19.2.2.
gitlab-rake gitlab:env:info
- Upgrade your self-managed GitLab EE (the gitlab/gitlab-ee image tag or the gitlab-ee package) to the patched release of your series.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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 cloud service credentials and private signing keys.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.