Is CVE-2026-19478 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-19478 being exploited in the wild.

How severe is CVE-2026-19478?

Critical severity, with a CVSS score of 9.4, published 17 August 2026.

Which products and versions are affected?

GitLab Community Edition 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, 19.2 before 19.2.4; GitLab Enterprise Edition 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, 19.2 before 19.2.4.

Is there a fix for CVE-2026-19478?

A patch was published on 2026-08-17: Patched versions released: 18.11.11, 19.0.8, 19.1.6, 19.2.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-19478 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-19478?

Check whether you run GitLab Community Edition or GitLab Enterprise Edition 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.

CVE-2026-19478: GitLab CE/EE code injection via GraphQL directive

CVE-2026-19478 · Severity: critical · CVSS 9.4 · Published 2026-08-17

GitLab Community Edition and Enterprise Edition contain a critical vulnerability that allows unauthenticated attackers to modify or delete public projects and user data through a flaw in GraphQL directive handling. This affects self-managed GitLab instances and could lead to data loss, unauthorized changes to repositories, and reputational damage. Immediate patching is required for all affected versions.

Technologies: GitLab Community Edition, GitLab Enterprise Edition. Vendors: GitLab.

Quick answers

Is CVE-2026-19478 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-19478 being exploited in the wild.
How severe is CVE-2026-19478?: Critical severity, with a CVSS score of 9.4, published 17 August 2026.
Which products and versions are affected?: GitLab Community Edition 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, 19.2 before 19.2.4; GitLab Enterprise Edition 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, 19.2 before 19.2.4.
Is there a fix for CVE-2026-19478?: A patch was published on 2026-08-17: Patched versions released: 18.11.11, 19.0.8, 19.1.6, 19.2.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-19478 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-19478?: Check whether you run GitLab Community Edition or GitLab Enterprise Edition 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

The vulnerability is a code injection issue in GraphQL directive processing that allows unauthenticated remote attackers to execute arbitrary operations. The flaw permits modification or deletion of public projects and user data without authentication or user interaction required. Attack vector is network-based with no preconditions (PR:N, UI:N). Affected versions include GitLab CE/EE 18.2–18.11.10, 19.0–19.0.7, 19.1–19.1.5, and 19.2–19.2.3. Patches are available in GitLab 18.11.11, 19.0.8, 19.1.6, and 19.2.4; immediate upgrade is strongly recommended.

Affected products

GitLab GitLab Community Edition 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, 19.2 before 19.2.4
GitLab GitLab Enterprise Edition 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, 19.2 before 19.2.4

Timeline

2026-08-17: disclosed: Vulnerability disclosed and patched versions released
2026-08-17: patched: Patched versions released: 18.11.11, 19.0.8, 19.1.6, 19.2.4

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.