CVE-2025-7000: GitLab · Insertion of Sensitive Information Into Sent Data
Affects GitLabSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium · 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 | 4.3 |
|---|
- Patch
- Available – fixed in 18.5.2, 18.4.4, 18.3.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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
Fixed versions are 18.3.6, 18.4.4, and 18.5.2 or later. Users should upgrade affected GitLab CE/EE instances to these versions to remediate the vulnerability. Since this is not a cloud service, remediation requires applying the official patches. No known exploits are reported in the wild.
Description
CVE-2025-7000 is a medium severity vulnerability in GitLab CE/EE that affects versions 17.6, 18.4, and 18.5 prior to their respective fixed releases. Under specific conditions, unauthorized users could view confidential branch names by accessing project issues linked to related merge requests. This issue involves the insertion of sensitive information into sent data, classified under CWE-201.