External risk intelligence

GitLab Duo Chat GraphQL Subscription Argument Allows Sensitive Data Exposure

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-87719

GitLab is commonly deployed as an internet-facing application or API gateway. While this specific vulnerability requires authenticated access to a specific feature, the underlying service is typically exposed to the public internet in standard production environments.

Deserialization

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical vulnerability in GitLab that could allow authenticated users with specific access to retrieve sensitive instance configurations and credentials. The issue arises from an improperly handled GraphQL argument that bypasses security measures, potentially exposing critical information.

A GitLab flaw could expose sensitive configurations and credentials.
It allows authenticated users to access critical instance data.
Confirm if Duo Chat and Advanced Search are relevant.

Attack Path

How an attacker could exploit the issue

An attacker with authenticated access to GitLab's Duo Chat feature could exploit this vulnerability. By sending a specially crafted GraphQL subscription argument, they could bypass serialization protections, leading to a server-side object lookup. This could then expose sensitive instance configurations and credentials.

Authenticated user required for access.
Triggered by a crafted GraphQL subscription argument.
Risk of exposing sensitive configurations and credentials.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an authenticated user with Duo Chat access to gain insight into GitLab's Advanced Search configurations and potentially expose sensitive credentials. This exposure could occur when a specially crafted GraphQL subscription argument is used, bypassing serialization protections and enabling a server object lookup.

Instance configurations and credentials at risk.
Specially crafted GraphQL arguments bypass protections.
Unauthorized access to sensitive system information.

Operational Fix

Recommended remediation, mitigation, and detection steps

GitLab instances with Duo Chat enabled are the primary concern for this vulnerability. Infrastructure or platform teams responsible for GitLab deployments should identify all instances, determine their exposure and criticality, and confirm ownership for remediation. Coordination with vendor management may be necessary if GitLab is a third-party service. The initial step involves asset inventory and risk assessment to prioritize affected systems.

Identify all GitLab instances.
Verify Duo Chat feature reachability.
Plan remediation with owners.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is GitLab and what is it used for?

GitLab is a comprehensive software development platform used by teams to manage the entire DevOps lifecycle. It provides tools for source code management, continuous integration and deployment (CI/CD), project tracking, and security monitoring within a single application.

What does CWE-502 mean for CVE-2026-87719?

CWE-502 refers to Deserialization of Untrusted Data. In this CVE, the application fails to properly secure how it processes incoming data objects. By manipulating GraphQL arguments, a user can trick the system into performing unauthorized operations, such as looking up server objects they should not access.

How is this vulnerability triggered?

An authenticated user must send a specifically crafted GraphQL subscription argument to the Duo Chat feature. The vulnerability does not trigger through standard UI interactions or public, unauthenticated API calls, as it relies on bypassing serialization protections via this specific GraphQL input path.

Is my GitLab instance at risk according to Halo Surface Signal?

Halo Surface Signal notes that GitLab is often deployed as an internet-facing application, making it highly visible. While the bug requires authenticated access to Duo Chat, the underlying service's typical public accessibility increases the overall risk profile for organizations running vulnerable versions.

What are the first steps to address this CVE?

Start by identifying all GitLab EE instances in your environment and verifying if the Duo Chat feature is enabled. Once identified, prioritize these systems for an update to a patched version, as listed in the advisory, to ensure serialization protections are restored.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.