CVE-2026-6352: Incorrect Authorization in GitLab
GitLab has remediated an issue in GitLab EE affecting all versions from 18.2 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with auditor-level access to modify compliance violation records due to improper authorization on certain GraphQL operations.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 18.11.7 - Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.0.4 - Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.1.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-6352?
The severity of CVE-2026-6352 is low with a score of 2.7.
How does CVE-2026-6352 impact GitLab users?
CVE-2026-6352 may allow an authenticated user with auditor-level access to modify compliance violation records.
Which versions of GitLab are affected by CVE-2026-6352?
CVE-2026-6352 affects GitLab EE versions prior to 18.11.7, 19.0.4, and 19.1.2.
How can I fix CVE-2026-6352?
To fix CVE-2026-6352, users are advised to upgrade GitLab to the latest versions 18.11.7, 19.0.4, or 19.1.2.
What type of vulnerability is CVE-2026-6352?
CVE-2026-6352 is categorized as an incorrect authorization vulnerability.