Summary
| Parameter | Value |
|---|---|
| CVE ID | CVE-2026-19478 |
| Alert Source | GitHub Advisory - Critical Vulnerability |
| CVE Publication Year | 2026 |
| Date Published | 2026-08-17 |
| Vendor | GitLab |
| Product | GitLab |
| CVSS Score | 9.4 (critical) |
| EPSS Score | No data |
| CISA KEV | No |
| Ransomware | Not confirmed |
Vulnerability Description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4 that under certain conditions could allow an unauthenticated user to remotely modify or delete public projects and user data via a GraphQL directive.
Required Actions
Apply vendor patches or mitigations as soon as available.
Who Is Affected?
This vulnerability affects GitLab (GitLab CE/EE). Check if your organization uses this software and requires updates.
Sources
Need help securing your systems? nFlo team offers vulnerability management and 24/7 SOC services. Contact us.
Frequently asked questions
What is the CVE-2026-19478 vulnerability?
CVE-2026-19478 is a security vulnerability discovered in GitLab's GitLab. The vulnerability has been assigned a CVSS score of 9.4 (critical severity). Any organization using this product should immediately verify their exposure and take appropriate remediation steps.
Who is affected by CVE-2026-19478?
This vulnerability affects users of GitLab's GitLab. Organizations using this solution should check whether their deployed version is vulnerable and apply available security patches or implement recommended workarounds.
How to protect against CVE-2026-19478?
Apply security patches released by GitLab or implement recommended workarounds. Regular vulnerability monitoring and prompt patch deployment are essential for effective protection against this type of threat.
What is the risk level of CVE-2026-19478?
The vulnerability has a CVSS score of 9.4 (critical severity). Successful exploitation could lead to compromise of organizational systems and data.
