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

> Authenticated users can redirect AI model requests to external endpoints, leaking cloud credentials and signing keys via SSRF in GitLab AI Gateway.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-827c-52wf-3g9x

## What is CVE-2026-75871?

CVE-2026-75871 is a high-severity server-side request forgery vulnerability in Gitlab Gitlab, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-75871?

It affects 1 product.


Products: Gitlab Gitlab.

## How do I fix CVE-2026-75871?

No fix has been published for CVE-2026-75871 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-75871 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75871 exists.

## Other vulnerabilities in Gitlab Gitlab

- [CVE-2026-97229](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild)
- [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75871 and fix it if it is affected.

What it is: CVE-2026-75871 is a high-severity server-side request forgery vulnerability in Gitlab Gitlab, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75871 exists.

Affected product: Gitlab Gitlab. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75871/ (Markdown: https://insights.sbomify.com/CVE-2026-75871/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75871
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75871
- OSV: https://osv.dev/vulnerability/CVE-2026-75871

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75871/
Summaries are generated and may contain mistakes; the official description above is the record.