GitLab · GitLab · published 2026-01-09

CVE-2025-3950Exposure of Private Personal Information to an Unauthorized Actor in GitLab

Routine No exploitation evidence; EPSS 0.3%.

CVE-2025-3950 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 19% of all CVEs. This GitLab vulnerability: CVSS 3.5 (v3.1). Fixed upstream in GitLab 18.7.1, 18.6.3, 18.5.5. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 18.7.1, 18.6.3, 18.5.5.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.7.1, 18.6.3, 18.5.5

    Upgrade to 18.7.118.6.318.5.5

    Why: CVE-2025-64720: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (20th pct)FIRST EPSS v2026.06.15
CVSS base score3.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.3 before 18.5.5, 18.6 before 18.6.3, and 18.7 before 18.7.1 that could have allowed a user to leak certain information by referencing specially crafted images that bypass asset proxy protection.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →