CVE-2025-1908
GitLab vulnerability
- Published24 Apr 2025
Description
An issue has been discovered in GitLab EE/CE that could allow an attacker to track users' browsing activities, potentially leading to full account take-over, affecting all versions from 16.6 before 17.9.7, 17.10 before 17.10.5, and 17.11 before 17.11.1.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:NAffected products
Remediation
Frequently asked
Is CVE-2025-1908 being actively exploited?
CVE-2025-1908 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.39%.
How severe is CVE-2025-1908?
CVE-2025-1908 has a CVSS 3.1 base score of 7.7, rated high. EPSS estimates a 0.39% probability of exploitation.
Which products are affected by CVE-2025-1908?
Affected products include GitLab.
How do I fix CVE-2025-1908?
Upgrade affected software to a fixed version, for example GitLab 17.9.7 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-1908 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.