CVE-2026-19478Known exploitationNetwork attack vector

Unauthenticated data tampering via GraphQL directive

Published Aug 17, 2026 · Updated Aug 17, 2026

Code injection in GitLab CE/EE before 18.11.11, 19.0.8, 19.1.6, and 19.2.4 allows remote attackers to modify or delete public projects and user data via GraphQL. GitLab's public advisory identifies a GraphQL directive as the entry point but does not name the directive or disclose how untrusted GraphQL input reaches code generation or state-changing operations. Exposure is limited to reachable self-managed instances with public data in scope; GitLab stated GitLab.com and GitLab Dedicated were already patched when the issue was disclosed.

CVSS severity9.4
Critical
EPSS probability5.81%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Code injection in GitLab CE/EE before 18.11.11, 19.0.8, 19.1.6, and 19.2.4 allows remote attackers to modify or delete public projects and user data via GraphQL. GitLab's public advisory identifies a GraphQL directive as the entry point but does not name the directive or disclose how untrusted GraphQL input reaches code generation or state-changing operations. Exposure is limited to reachable self-managed instances with public data in scope; GitLab stated GitLab.com and GitLab Dedicated were already patched when the issue was disclosed.

The record

CVE
CVE-2026-19478
Published
Aug 17, 2026
Updated
Aug 17, 2026
Vendor
GitLab
Product
GitLab
Classifications
CWE-94, T1565.001, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 17, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=18.2 <18.11.11
  2. Affected versionversion=19.0 <19.0.8
  3. Affected versionversion=19.1 <19.1.6
  4. Affected versionversion=19.2 <19.2.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

GitLab · GitLabversion=18.2 <18.11.11; version=19.0 <19.0.8; version=19.1 <19.1.6; version=19.2 <19.2.4

Published CVSS scores

9.4GitLabCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationReported
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-94Improper Control of Generation of Code ('Code Injection')
T1565.001Stored Data Manipulation
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Reported exploitation

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo