CVE-2026-11827: Insufficiently Protected Credentials in GitLab
GitLab has remediated an issue in GitLab EE affecting all versions from 9.5 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 maintainer-role permissions to obtain another user's stored credentials due to improper authorization controls.
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-11827?
CVE-2026-11827 has a medium severity rating of 4.9.
How do I fix CVE-2026-11827?
To fix CVE-2026-11827, upgrade to GitLab versions 18.11.7, 19.0.4, or 19.1.2 or later.
Who is affected by CVE-2026-11827?
CVE-2026-11827 affects authenticated users with maintainer-role permissions in specific GitLab versions.
What kind of vulnerability is CVE-2026-11827?
CVE-2026-11827 is an insufficiently protected credentials vulnerability in GitLab.
Can CVE-2026-11827 lead to credential leaks?
Yes, CVE-2026-11827 could allow an authenticated user to obtain another user's stored credentials due to insufficient protection.