CVE-2026-110264
CVE-2026-110264: How to Detect & Patch GitLab 10.0 Regex RCE
Executive Vulnerability Brief & Attack Vector
GitLab patches maximum-severity CVSS 10.0 flaw CVE-2026-110264 allowing unauthenticated RCE across 12 years of releases. Here is how to defend.
Terminal Triage Runbook & Exposure Verification
curl -I -s -k -m 5 "https://TARGET-HOST:PORT/" | grep -Ei "(server|x-powered-by|gitlab)"Quick probe to verify remote server header exposure and identify listening versions without sending destructive payloads.
ss -tulpn | grep -Ei "(80|443|8080|8443|gitlab)" ; ps aux | grep -Ei "gitlab"Inspect active listening sockets and running process arguments on suspected victim hosts to confirm if exposed services are active.
find /tmp /var/tmp /dev/shm -mtime -7 -type f -exec ls -la {} + 2>/dev/nullSearch Linux scratch directories for dropped secondary payloads, ELF droppers, or staged reverse shells executed via this vulnerability.
Production Detection Queries (Sentinel KQL & Sigma)
The vulnerability stems from an integer overflow during regular expression compilation inside Ruby's bundled Onigmo regex engine, enabling unauthenticated attackers to corrupt heap memory and execute arbitrary code via crafted patterns.
DeviceProcessEvents
| where InitiatingProcessFileName in~ ("puma", "sidekiq", "ruby", "gitlab-workhorse")
| where FileName in~ ("sh", "bash", "dash", "curl", "wget", "nc", "python", "python3")
| project
TimeGenerated,
DeviceId,
DeviceName,
InitiatingProcessFileName,
InitiatingProcessCommandLine,
FileName,
ProcessCommandLine,
AccountName
| order by TimeGenerated descCampaign Indicators of Compromise (9 IOCs)
Have updated exploit telemetry, unlisted PoC repository, or triage runbook correction for CVE-2026-110264?