CVE-2026-8667: Incorrect Authorization in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.6 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer role to modify certain package registry metadata without the required maintainer-level permissions due to improper authorization checks.
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.6 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 19.1.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 19.2.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-8667?
The severity of CVE-2026-8667 is rated as medium with a score of 4.3.
How do I fix CVE-2026-8667?
To fix CVE-2026-8667, upgrade GitLab CE/EE to versions 19.0.6, 19.1.4, or 19.2.2 or later.
What is the impact of CVE-2026-8667?
CVE-2026-8667 could allow an authenticated user with a developer role to modify package registry metadata without proper authorization.
Which versions of GitLab are affected by CVE-2026-8667?
CVE-2026-8667 affects GitLab CE/EE versions from 17.6 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2.
Is CVE-2026-8667 present in the latest GitLab versions?
CVE-2026-8667 is not present in GitLab versions 19.0.6, 19.1.4, or 19.2.2 and later, as they have been remediated.