Deserialization of Untrusted Data in GitLab
3 public exploits exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in GitLab 18.11.12, GitLab 19.0.9, GitLab 19.1.8 and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| GitLab | GitLab | >=18.3 <18.11.12, >=19.0 <19.0.9, >=19.1 <19.1.8, >=19.2 <19.2.6, >=19.3 <19.3.2 | 18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2 |
Exploit evidence
3 public sources
Vendor advisories
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in GitLab, strongest first
Embed
A live severity badge for an advisory, README or ticket