GitLab CE/EE affecting all · GitLab Has Remediated an Issue
Affects GitLab Community Edition and Enterprise EditionSource GCVE Database
Exploited in the wild · KEV due 14 Sep 2026 · public exploit available (Metasploit) · 97% EPSS · fixed in 19.3.2 : patch GitLab Community Edition and Enterprise Edition now.
Data as of 28 Oct 2026, 05:12 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
- EPSS
- 97.3% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 19.3.2, 19.2.6, 19.1.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 12 Sep 2026
Detectable: evidence found.
nuclei template: GitLab CE/EE <=19.1.7/19.2.5/19.3.1 - Arbitrary File Read
Weaponised: evidence found.
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 1 day before disclosure
Observed by OffSeq MirageSeen by Mirage: evidence found.
1 exposed host found; no attack traffic recorded
Timeline
Added to CISA KEV (opens in a new tab)
exploitation confirmed
, 1 day before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 21 hours after disclosure
KEV remediation due
US federal deadline
, 2 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), OffSeq Mirage (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade gitlab to 19.3.2, 19.2.6 or 19.1.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
RubyGemsgitlabpkg:gem/gitlabOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.