CVE-2026-19478: Improper Control of Generation of Code ('Code Injection') in GitLab

Critical 9.1 EPSS 2.2% GitLab CE/EE

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4 that under certain conditions could allow an unauthenticated user to remotely modify or delete public projects and user data via a GraphQL directive.

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

  1. Check whether you run GitLab CE/EE and which version (commands below).
  2. Install the fixed version for your system: see “Patch it” below.
  3. Omnibus: the package upgrade runs gitlab-ctl reconfigure and restarts services; check with sudo gitlab-ctl status

Affected and fixed versions

Affected:

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Debian
not in distro repos: packages.gitlab.com gitlab-ce / gitlab-ee
Ubuntu
not in distro repos: packages.gitlab.com gitlab-ce / gitlab-ee
RHEL, AlmaLinux, Rocky, Oracle
not in distro repos: packages.gitlab.com gitlab-ce / gitlab-ee
Fedora
not packaged
SUSE / openSUSE
not in distro repos: packages.gitlab.com gitlab-ce / gitlab-ee
Amazon Linux
not in distro repos: packages.gitlab.com gitlab-ee
Arch Linux
sudo pacman -Syu
Alpine
apk update && apk upgrade gitlab-runner (runner only)
FreeBSD
pkg update && pkg upgrade gitlab-ce

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

Sources

Page generated automatically from official sources on 2026-11-03 18:05 UTC. Always confirm with your vendor's advisory.