CVE-2025-7659
Gitlab 18.2.0 – 18.6.6
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:NSummary
CVE-2025-7659 is a high-severity Origin Validation Error (CWE-346) vulnerability in Gitlab Gitlab. Its CVSS base score is 8.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique DHCP Spoofing (T1557.003); ranked at the 8th 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-4 (Information Flow Enforcement) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-7659 is a vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE), affecting all versions from 18.2 prior to 18.6.6, 18.7 prior to 18.7.4, and 18.8 prior to 18.8.4. The flaw arises from incomplete validation in the Web IDE component, enabling an unauthenticated user to steal tokens and access private repositories. It carries a CVSS v3.1 base score of 8.0 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N) and maps to CWE-346 (Origin Validation Error).
The attack requires network access with no privileges, high complexity, and user interaction, but successful exploitation allows an unauthenticated attacker to steal authentication tokens. This grants unauthorized read and potentially write access to private repositories, resulting in high impacts to confidentiality and integrity across a changed scope.
GitLab has remediated the issue via patches in versions 18.6.6, 18.7.4, and 18.8.4, as detailed in their February 10, 2026 patch release notes. Security teams should prioritize upgrading affected instances. Additional technical details are available in GitLab's issue tracker (gitlab.com/gitlab-org/gitlab/-/issues/555440) and the originating HackerOne report (hackerone.com/reports/3234976).
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-207019
Vulnerability Data
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an unauthenticated user to steal tokens and access private repositories by abusing incomplete validation…
more
in the Web IDE.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Information flow enforcement directly requires validating the source of data before allowing transmission or receipt.
Device identification and authentication mandates verifying the source before establishing connections.
Session authenticity mechanisms require validation that communications originate from the expected party.
Boundary protection at interfaces enforces checks on the origin of incoming communications.
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.
Authentication directly verifies the source of users/services/hardware, mitigating origin validation failures.
Verifying identity assertions enforces origin validation for conveyed claims.
Documenting authorized flows supports origin validation by defining expected sources.
Protecting networks from unauthorized access requires origin checks on communication sources.
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.
Network security controls enforce origin validation at network boundaries.
Security of network services includes validating the authenticity of service endpoints.
Network segregation reduces exposure but does not directly validate origins.
Application security requirements explicitly call for origin validation of inputs and communications.
Secure architecture principles encourage origin checks but do not mandate them.
Secure coding practices include implementing proper origin validation to prevent spoofing.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-346
- V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-346
- V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-346