Skip to main content
CVE-2026-8667VulnerabilityPublished

GitLab CE/EE affecting all · GitLab Has Remediated an Issue

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 4.3 Medium · fixed in 19.2.2 : update affected systems when convenient.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 19.2.2, 19.1.4, 19.0.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

AI-suggested

Upgrade GitLab CE/EE to versions 19.0.6 or later for the 17.6 branch, 19.1.4 or later for the 19.1 branch, and 19.2.2 or later for the 19.2 branch to remediate this issue. No other mitigation actions are indicated.

Description

A vulnerability in GitLab CE/EE versions from 17.6 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 allowed authenticated users with developer role to modify certain package registry metadata without maintainer-level permissions due to improper authorization checks. This issue has been remediated by GitLab.

References

Community reviews

Loading reviews…