GitLab CE/EE affecting all · GitLab Has Remediated an Issue
Source GCVE Database
Not known to be exploited · CVSS 8.5 High · fixed in 19.2.2 : patch affected systems soon.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% 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:H/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
AI-suggested
Upgrade affected GitLab CE/EE instances to versions 19.0.6 or later for the 18.8 series, 19.1.4 or later for the 19.1 series, and 19.2.2 or later for the 19.2 series. These versions contain the official fixes for this vulnerability. No other mitigation steps are indicated by the vendor advisory.
Description
A path traversal vulnerability in GitLab CE/EE versions from 18.8 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 could allow an authenticated user to achieve remote code execution. This issue has been remediated in the specified fixed versions.