CVE-2025-6945: GitLab · Command Injection
Affects GitLabSource GCVE Database
Not known to be exploited · CVSS 3.5 Low · fixed in 18.5.2 : update GitLab when convenient.
Data as of 13 Nov 2026, 19:39 UTC
Thin evidence
One scorer or none| CNA (GitLab) | CVSS 3.1 | 3.5 |
|---|
- Patch
- Available – fixed in 18.5.2, 18.4.4, 18.3.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade GitLab to 18.5.2, 18.4.4 or 18.3.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GitLab GitLab | Affected
| Fixed in
|
AI-suggested
GitLab has released official fixes for this vulnerability in versions 18.3.6, 18.4.4, and 18.5.2. Users should upgrade to these or later versions to remediate the issue. No additional mitigation actions are indicated.
Description
CVE-2025-6945 is a command injection vulnerability in GitLab Enterprise Edition affecting versions 17.8 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2. It allows an authenticated attacker to leak sensitive information from confidential issues by injecting hidden prompts into merge request comments. The vulnerability has a low CVSS score of 3.5 and does not impact integrity or availability.