GitLab · GitLab · published 2026-08-12
CVE-2026-8667Incorrect Authorization in GitLab
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-8667 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 34% of all CVEs. This GitLab vulnerability: CVSS 4.3 (v3.1). Fixed upstream in GitLab 19.2.2, 19.1.4, 19.0.6. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in GitLab 19.2.2, 19.1.4, 19.0.6.
Patch events
DevOpsGitLab
GitLab security releases: 19.2.2, 19.1.4, 19.0.6
Upgrade to
19.2.219.1.419.0.6Why: CVE-2026-4879: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (34th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 4.3 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- GitLab GitLab
17.6to before19.0.6(affected)19.1to before19.1.4(affected)19.2to before19.2.2(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.