Quick answers
- Is CVE-2026-93577 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93577 being exploited in the wild.
- How severe is CVE-2026-93577?
- Critical severity, with a CVSS score of 9.9, published 24 September 2026.
- Which products and versions are affected?
- GitLab EE 19.2 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1; GitLab CE 19.2 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1.
- Is there a fix for CVE-2026-93577?
- A patch was published on 2026-09-23: Versions 19.4.1, 19.3.3, 19.2.7 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93577 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-93577?
- Check whether you run GitLab EE or GitLab CE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An integer overflow in the regular expression compiler component allows authenticated users to trigger arbitrary code execution when parsing specially crafted regex patterns in CI/CD configurations. The vulnerability requires authentication and network access, but no user interaction. Exploitation grants complete remote code execution as the GitLab service account. Patches are available in versions 19.2.7, 19.3.3, and 19.4.1.
Affected products
- GitLab CE 19.2 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1
- GitLab EE 19.2 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1
Timeline
- 2026-09-24: disclosed
- 2026-09-23: patched: Versions 19.4.1, 19.3.3, 19.2.7 released