CVE-2025-5101
Gitlab ≤ 18.1.5
Raw vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:N/I:H/A:NSummary
CVE-2025-5101 is a medium-severity Code Injection (CWE-94) vulnerability in Gitlab Gitlab. Its CVSS base score is 5.0 (Medium).
Operationally, ranked at the 3th 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 SI-10 (Information Input Validation) and SI-7 (Software, Firmware, and Information Integrity) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-25949
Vulnerability Data
An issue has been discovered in GitLab CE/EE affecting all versions before 18.1.5, 18.2 before 18.2.5, and 18.3 before 18.3.1 that under certain conditions could have allowed an authenticated attacker to distribute malicious code that appears harmless in the web…
more
interface by taking advantage of ambiguity between branches and tags during repository imports.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
V1.3.1
Mitigating Controls (NIST 800-53 r5) AI
Verifies integrity of imported repository content to detect branch/tag ambiguity that would otherwise allow malicious code to be presented as harmless.
Requires validation of all input data during repository imports, directly blocking exploitation of branch versus tag name ambiguity.
Scans or filters imported code for malicious payloads before it is accepted into the repository.
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.
PR.PS-06's SDLC practices directly target injection flaws via secure coding and testing (mostly), yet as a single broad outcome it leaves many code-generation specifics unaddressed (partial).
PR.DS-10 protects runtime data confidentiality/integrity but has no bearing on neutralizing externally influenced input during code generation, so neither direction shows any preventive effect.
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.
Banning unapproved code samples and unauthenticated web services, combined with secure-coding standards and SAST, prevents the dynamic generation or inclusion of attacker-supplied code.
Controls that restrict unauthorized or malicious code from being introduced via external networks or removable media limit opportunities for an attacker to inject and execute arbitrary code.