Cyber Resilience

CVE-2025-12669

Gitlab 15.11.0 – 18.9.7

Published
14 May 2026
Modified
17 June 2026
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS Score 0.0018 7th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-12669 is a medium-severity Code Injection (CWE-94) vulnerability in Gitlab Gitlab. Its CVSS base score is 5.4 (Medium).

Operationally, ranked at the 7th 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-15 (Information Output Filtering) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.11 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to inject HTML and JavaScript into email notifications sent to other…

more

users due to improper input sanitization.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-1606Same product: Gitlab Gitlab
CVE-2024-3958Same product: Gitlab Gitlab
CVE-2023-6051Same product: Gitlab Gitlab
CVE-2023-3401Same product: Gitlab Gitlab
CVE-2025-5101Same product: Gitlab Gitlab
CVE-2023-1178Same product: Gitlab Gitlab
CVE-2021-22205Same product: Gitlab Gitlab
CVE-2023-5226Same product: Gitlab Gitlab
CVE-2023-5512Same product: Gitlab Gitlab
CVE-2026-1516Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
15.11.0 — 18.9.7 · 15.11.0 — 18.9.7 · 18.10.0 — 18.10.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SI-15 Information Output Filtering
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.3.1

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires validation and sanitization of all inputs before they are used to generate outputs such as email notifications, blocking the HTML/JS injection vector.

prevent

Requires filtering of information outputs (including email content) to remove or encode potentially malicious markup before delivery to users.

detect

Provides integrity checks that can detect unauthorized or unexpected modifications to notification templates or generated content after the fact.

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 mostly match
prevents

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 none match
prevents

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.

prevents

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.

none

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.

References