CVE-2025-6195
Gitlab 13.7.0 – 18.4.5
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2025-6195 is a medium-severity Forced Browsing (CWE-425) vulnerability in Gitlab Gitlab. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Information Repositories (T1213); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-199757
Vulnerability Data
GitLab has remediated an issue in GitLab EE affecting all versions from 13.7 before 18.4.5, 18.5 before 18.5.3, and 18.6 before 18.6.1 that could have allowed an authenticated user to view information from security reports under certain configuration conditions.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
The vulnerability allows an authenticated user to access security reports under specific conditions, which aligns with T1213 (Data from Information Repositories) as security reports represent data stored in an information repository (GitLab).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces authorization checks on security report resources so authenticated users cannot bypass access to view restricted data.
Limits user privileges to only those required, reducing the chance that configuration conditions expose security reports to unauthorized viewers.
Enforces information flow rules between users and security report data, blocking unauthorized disclosure paths present in the vulnerable GitLab configuration.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect forced-browsing flaws, but the control itself does not prevent them in production.
Information access restriction implements the technical enforcement that directly blocks unauthorized direct requests.
Access control policy directly requires authorization checks on all resources, preventing forced browsing.
Managing access rights ensures every URL/script/file is explicitly authorized, mitigating direct request attacks.
Privileged access rights control enforces least-privilege checks on restricted endpoints.
Secure SDLC can include authorization design, yet the control itself does not guarantee runtime enforcement.