# CVE-2026-87719: Deserialization of Untrusted Data in GitLab

> Authenticated users with Duo Chat access can bypass serialization to read sensitive credentials and instance configurations via crafted GraphQL arguments.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** BIT-gitlab-2026-87719, GHSA-prp4-5w2g-8v2c, MINI-6489-2h8p-3xp9, MINI-7c26-m7p6-9w6x, MINI-px6q-vhwf-4v3g

## What is CVE-2026-87719?

CVE-2026-87719 is a critical unsafe deserialization vulnerability in Gitlab Gitlab, published on 12 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could allow an authenticated user with Duo Chat access to obtain Advanced Search instance configurations and sensitive credentials using a specially crafted GraphQL subscription argument to bypass serialization and perform server object lookup.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

1 open source package ship an affected version, including gitlab. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab` | Bitnami | From 18.3.0 | 19.1.8, 19.2.6, 19.3.2 |

Products: Gitlab Gitlab.

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

Upgrade gitlab to a fixed version for your release line: 19.1.8, 19.2.6 or 19.3.2.

## Is CVE-2026-87719 being exploited?

There is no known exploitation of CVE-2026-87719 in the wild and no public exploit code.

## 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-87719 and fix it if it is affected.

What it is: CVE-2026-87719 is a critical unsafe deserialization vulnerability in Gitlab Gitlab, published on 12 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-87719 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitlab (Bitnami): affected from 18.3.0; fixed in 19.1.8, 19.2.6, 19.3.2

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-87719/ (Markdown: https://insights.sbomify.com/CVE-2026-87719/index.md)
```

## Sources

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

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