GitLab: Permissive Regular Expression
CVE-2026-14814 is a high-severity permissive regular expression vulnerability in GitLab, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 19.2.8, 19.3.5, 19.4.2 as the first without the flaw, so updating GitLab to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.39% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update GitLab to 19.2.8 or 19.3.5 or 19.4.2, whichever matches your release line, or a later version.
- Read the advisory on docs.gitlab.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GitLab | GitLab | before 19.2.8; 19.3 up to, but not including, 19.3.5; 19.4 up to, but not including, 19.4.2 | 19.2.8, 19.3.5, 19.4.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N. Scored by CNA (gitlab.com).
Official description
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' CI/CD pipelines to execute specially crafted content and potentially exposing protected environment variables, due to improper validation of repository references.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Permissive Regular Expression
The product uses a regular expression that does not sufficiently restrict the set of allowed values.
How developers prevent this class of flaw
- When applicable, ensure that the regular expression marks beginning and ending string patterns, such as /^string$/ for Perl.
More Permissive Regular Expression vulnerabilities (CWE-625)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
- gitlab.com/gitlab-org/gitlab/-/work_items/604950Issue Tracking
- hackerone.com/reports/3832707Permissions Required
Other vulnerabilities in GitLab
- 7.1 High severity
- 8.2 High severity
- 7.5 High severity
- 10.0 Critical severity
- 10.0 Critical severity
- 7.3 High severity
Recent Permissive Regular Expression vulnerabilities
- 8.6 High severity
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.