Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-19478 – Unauthenticated Code Injection / Data Modification via GraphQL – GitLab CE/EE 18.2–

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-19478 is a critical code injection vulnerability (CWE-94) in GitLab Community Edition and Enterprise Edition. Under certain conditions, an unauthenticated attacker can exploit a GraphQL directive to remotely modify or delete public projects and user data. GitLab rates this issue 9.4 (Critical) and has released patched versions for all affected release lines.

Technical details

  • Root cause: improper control of code generation ("code injection") triggered through a GraphQL directive processed by GitLab’s GraphQL API.
  • Trigger conditions: exploitable under "certain conditions" against the GraphQL endpoint; GitLab has not published further exploitation prerequisites in the public advisory.
  • Attack vector: Network — no authentication and no user interaction are required (PR:N, UI:N).
  • Impact: an unauthenticated actor can remotely modify or delete public projects and user data, affecting data integrity and availability (I:H, A:H), with limited confidentiality impact (C:L).

Affected software

  • GitLab CE/EE 18.2 up to (but not including) 18.11.11
  • GitLab CE/EE 19.0 up to (but not including) 19.0.8
  • GitLab CE/EE 19.1 up to (but not including) 19.1.6
  • GitLab CE/EE 19.2 up to (but not including) 19.2.4

Severity

CVSS v3.1 Base Score: 9.4 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade GitLab CE/EE to 18.11.11, 19.0.8, 19.1.6, 19.2.4, or later — the fixed versions published by GitLab in its August 17, 2026 patch release.
  • If immediate patching is not possible, restrict network access to the GitLab instance (particularly the GraphQL API endpoint) to trusted sources until the upgrade can be applied, since no other workaround has been published by GitLab.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Rendered page (meta tag og:site_name): GitLab
  • Raw response body: gon.version = 'X.X.X', "gitlab_version":"X.X.X", <meta content='https://…/assets/gitlab_logo-, <header class='navbar navbar-fixed-top navbar-gitlab
  • JavaScript object present once the page runs: GitLab, gl.dashboardOptions

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge