CVE-2026-9694
Gitlab 15.9.0 – 18.10.8
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-9694 is a low-severity Improper Neutralization of Substitution Characters (CWE-153) vulnerability in Gitlab Gitlab. Its CVSS base score is 2.6 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 11th 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) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-36224
Vulnerability Data
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions, could have allowed an unauthenticated user to impersonate the GitLab Support Bot and inject…
more
arbitrary content via a specially crafted Service Desk email reply due to improper neutralization in email template processing.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.9V1.2.10
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly requires neutralizing or rejecting dangerous substitution characters before they reach a downstream interpreter.
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.
Secure SDLC practices directly require input validation and neutralization of substitution characters.
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 substitution-character flaws but does not itself implement neutralization.
Secure development lifecycle mandates input validation and sanitization that directly prevents substitution-character injection.
Application security requirements explicitly call for neutralizing special elements before downstream processing.
Secure coding standards require proper neutralization of substitution characters in all input handling.