EUVD-2026-85730
GHSA-wqwg-376r-c226
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Network-reachable and low-privilege authenticated (PR:L, needs CI/CD config rights), but 'certain conditions' for the overflow warrant AC:H; server RCE with instance-wide pivot justifies S:C and full C/I/A:H.
Primary rating from Vendor (GitLab).
CVSS VectorVendor: GitLab
Lifecycle Timeline
3DescriptionCVE.org
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially crafted regular expression in a CI/CD configuration.
Articles & Coverage 1
AnalysisAI
Authenticated code execution on the GitLab server is possible in GitLab CE/EE 19.2 through 19.4.0, where an integer overflow triggered while compiling a specially crafted regular expression in a CI/CD configuration can be leveraged to run arbitrary code with the privileges of the GitLab application. The attacker must hold a GitLab account with enough project privileges to create or modify CI/CD configuration (typically Developer or higher on a project), and exploitation only occurs 'under certain conditions,' so it is not universally triggerable; the vendor-assessed vector is PR:L with scope change, and our independent assessment raises attack complexity to High (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H). …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
No credit card · 7-day full trial
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires an authenticated GitLab account (PR:L) with sufficient project privileges to define or modify CI/CD configuration - i.e., the ability to submit a .gitlab-ci.yml (typically a Developer or higher role on some project). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuine high-priority vulnerability, not a high-CVSS-but-low-real-risk case. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patch: upgrade to GitLab CE/EE 19.2.7, 19.3.3, or 19.4.1 (or later) - 19.4.1 is the patch release documented at https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-1-released/, with fixes for the 19.2 and 19.3 branches backported to 19.2.7 and 19.3.3 respectively; the technical detail is tracked in https://gitlab.com/gitlab-org/gitlab/-/work_items/629758 and the researcher report at https://hackerone.com/reports/3995696. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory every GitLab CE/EE instance and identify those running 19.2 through 19.4.0 (authenticated exploitation is possible via the PR:L vector); immediately shrink the exposed population by auditing project memberships that grant Developer or higher and removing stale, service, or over-privileged accounts, and by restricting who may create or modify CI/CD configuration. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af
Unauthenticated arbitrary file read in GitLab CE/EE lets remote attackers retrieve files from the GitLab server via the
The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x
A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows
Sensitive credential and configuration disclosure in GitLab Enterprise Edition allows an authenticated user with Duo Cha
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Authenticated users who can define or modify a CI/CD configuration can achieve remote code execution on GitLab CE/EE ser
Unauthenticated path traversal in the @zereight/mcp-gitlab Model Context Protocol server prior to version 2.1.27 allows
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. Rated critical severity (CVSS 9.8)
Same weakness CWE-190 – Integer Overflow or Wraparound
View allShare
External POC / Exploit Code
Leaving vuln.today