Security Resilience

CVE-2026-14814

Gitlab ≤ 19.2.8

Published
13 October 2026
Modified
14 October 2026
Patch / advisory
CVSS Score v3.1 8.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS Score 0.0025 15th percentile
Risk Priority 55 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-14814 is a high-severity Permissive Regular Expression (CWE-625) vulnerability in Gitlab Gitlab. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 15th 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

Vulnerability Data

GitLab has remediated an issue in GitLab CE/EE affecting all versions before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed a user to poison cached responses for raw repository files, causing targeted users'…

more

CI/CD pipelines to execute specially crafted content and potentially exposing protected environment variables, due to improper validation of repository references.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001 Data Obfuscation Command And Control
Adversaries may obfuscate command and control traffic to make it more difficult to detect.
T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-2995Same product: Gitlab Gitlab
CVE-2023-5933Same product: Gitlab Gitlab
CVE-2025-11990Same product: Gitlab Gitlab
CVE-2026-5816Same product: Gitlab Gitlab
CVE-2026-1184Same product: Gitlab Gitlab
CVE-2026-87719Same product: Gitlab Gitlab
CVE-2026-93577Same product: Gitlab Gitlab
CVE-2026-97229Same product: Gitlab Gitlab
CVE-2026-1458Same product: Gitlab Gitlab
CVE-2026-10733Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
≤ 19.2.8 · ≤ 19.2.8 · 19.3.0 — 19.3.5

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 requires validity checks on inputs, directly stopping permissive regex patterns from being used for validation.

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 partial match
blocks

Secure SDLC practices directly require robust input-validation regex and testing that would prevent permissive patterns.

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.

blocks

Secure development lifecycle requires validation of input mechanisms, including regex, reducing permissive patterns.

blocks

Application security requirements mandate strict input validation rules that would catch overly permissive regex.

prevents

Secure coding standards directly prohibit permissive regex and enforce strict pattern validation.

finds

Security testing can detect permissive regex through fuzzing or negative test cases.

References