AI analysis
GitLab EE contains a critical (CVSS 9.9) deserialization flaw (CWE-502) in which an authenticated user with Duo Chat access can pass a specially crafted GraphQL subscription argument that bypasses serialization and performs a server object lookup. Via this bypass, the attacker can obtain Advanced Search instance configurations and the sensitive credentials they contain. Because the attack requires only a low-privileged account with Duo Chat access over the network, with no user interaction, any EE deployment where Duo Chat is enabled is potentially exposed, including both self-managed instances and GitLab.com. Affected versions are EE 18.3 and later before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2. No public proof-of-concept or CISA KEV listing exists for this CVE as of now, though related GitLab flaws disclosed in the same cycle are reportedly drawing internet-wide probing.
What to do: Upgrade GitLab EE to 19.3.2, 19.2.6, or 19.1.8 depending on the version track in use. Until patched, restrict Duo Chat access to trusted users or disable it where feasible, and audit logs for unusual GraphQL subscription activity by authenticated Duo Chat users. After upgrading, rotate Advanced Search (Elasticsearch/OpenSearch) credentials and review search cluster configurations for signs of access.
Affected
| GitLab EE | all versions from 18.3 before 19.1.8; 19.2 before 19.2.6; 19.3 before 19.3.2 |
Estimated exposure
largelikely hundreds of thousands of paid-tier (Duo-enabled) users across GitLab.com and self-managed EE instances — Duo Chat is gated to GitLab Premium/Ultimate subscriptions, so exposure is a subset of GitLab's very large installed base (tens of millions of GitLab.com accounts and tens of thousands of internet-exposed self-managed instances per public…
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description
GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 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.