CVE-2026-6267: Insertion of Sensitive Information Into Sent Data in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with Developer role to access unauthorized information due to insufficient access controls on internal request handling.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 19.0.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 19.1.3 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 19.2.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-6267?
The severity of CVE-2026-6267 is rated as high with a score of 8.5.
How do I fix CVE-2026-6267?
To fix CVE-2026-6267, upgrade GitLab CE/EE to version 19.0.5 or later, 19.1.3 or later, or 19.2.1 or later.
What versions of GitLab are affected by CVE-2026-6267?
CVE-2026-6267 affects GitLab CE/EE versions from 10.1.0 up to but not including 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1.
Who is vulnerable to CVE-2026-6267?
Authenticated users with a Developer role in the impacted versions of GitLab may be vulnerable to CVE-2026-6267.
What type of information can be accessed due to CVE-2026-6267?
CVE-2026-6267 can allow unauthorized access to sensitive information due to insufficient access control.