GPU VulnDB

Database/Control plane, storage & DevOps

GitLab CE/EE: unauthenticated remote code execution via integer overflow in regex compilation

CVSS 10.0CVE-2026-110264Control plane, storage & DevOpscurated

Impact

An unauthenticated request carrying a crafted regular expression triggers an integer overflow during compilation and lets the attacker run arbitrary code on the GitLab server. On a GPU fleet GitLab is usually the CI/CD and source-of-truth plane: it holds runner registration tokens, container registry credentials, cluster kubeconfigs and deploy keys. Code execution there is a path into the build runners and from them into the image supply chain that GPU nodes pull from. NVD records CVSS 10.0 with a scope change, consistent with full compromise of the host and everything the instance trusts.

Who can reach it

Anyone who can reach the GitLab HTTP endpoint. No authentication required, so any instance exposed to the internet or to a broad internal network is reachable; self-managed instances behind SSO-only ingress are correspondingly harder to hit.

What to do

Upgrade to 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3 or 19.5.1 per the GitLab patch release, then restart the GitLab services - a short control-plane outage, no GPU node impact. Running jobs are interrupted by the restart, so drain or let the current CI queue finish first. If the instance is internet-facing and cannot be patched immediately, restrict ingress to known networks; after patching, rotate runner tokens and registry credentials since pre-patch compromise cannot be ruled out from the record.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.