Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-110264 – Unauthenticated RCE (Integer Overflow) – GitLab CE/EE 7.0 to 19.5.0 (before 18.11.

Be the first to know when new zero-days emerge:

Summary

CVE-2026-110264 is an Integer Overflow or Wraparound vulnerability (CWE-190) in GitLab that can allow an unauthenticated user to execute arbitrary code on the server. It carries a CVSS v3.1 base score of 10.0 (Critical). GitLab has patched it in its 19.5.1 critical patch release and the corresponding backports.

Technical details

  • Root cause: an integer overflow or wraparound occurs during compilation of specially crafted regular expressions.
  • Trigger conditions: GitLab states that arbitrary code execution is possible "under certain conditions". It has not published what those conditions are.
  • Attack vector: network, with no authentication, privileges, or user interaction required.
  • Impact: arbitrary code execution on the GitLab server, with high impact to confidentiality, integrity, and availability and a changed scope.
  • GitLab.com and GitLab Dedicated are reported as already protected, so action falls to self-managed installations.

Affected software

  • GitLab 7.0 through 18.11.12
  • GitLab 19.0 through 19.0.9
  • GitLab 19.1 through 19.1.8
  • GitLab 19.2 through 19.2.8
  • GitLab 19.3 through 19.3.5
  • GitLab 19.4 through 19.4.2
  • GitLab 19.5.0

Releases such as 19.4.2, 19.3.5, and 19.2.8 remain affected, so patching to those is not sufficient.

Severity

CVSS v3.1 base score: 10.0 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: upgrade self-managed GitLab to a fixed release: 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, or 19.5.1 (or later).
  • Instances running 18.10 or older have no fixed release on their branch and must upgrade to 18.11.13 or later, which may take several upgrade steps.
  • No workaround has been published, so upgrading is the only remediation.
  • Until patching is complete, limit network exposure of self-managed GitLab instances where possible.

References

Get a free Attack Surface scan to see if you’re exposed.

Get a free Attack Surface scan to see if you’re exposed.

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge