Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-19478: Unauthenticated GraphQL Code Injection in GitLab CE/EE

Published Aug 17, 2026 · Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days5 mentions · peak 4 in a dayToday
CVSS9.1Critical · v3.1
EPSS2.2%82nd percentile
CISA KEVNoNot listed
In the wildReported19 exploitation records in Mallory
Vendor
GitLab
IdentifiersCVE-2026-19478CWE-94 · Improper Control of Generation of…

CVE-2026-19478 is a critical code injection vulnerability in GitLab Community Edition and Enterprise Edition GraphQL directive handling. Improper validation and unsafe parsing associated with the @gl_introduced directive can permit authorization bypass and anonymous state-changing operations against public resources. Under certain conditions, an unauthenticated remote attacker can modify or delete public projects and user data. Affected versions are 18.2 through versions before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4. The vulnerability has a CVSS v3.1 score of 9.4. Exploitation attempts were observed against honeypots shortly after disclosure; arbitrary host-level code execution and full instance takeover are not established.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation primarily compromises integrity and availability through unauthorized modification or deletion of public projects, repositories, and user data. Potential consequences include repository loss, falsified merge records, maintainer access restrictions, downstream build failures, and delayed security updates. Unauthorized project changes could also undermine software delivery workflows. These downstream consequences are potential impacts, not confirmed customer incidents. The CVSS assessment assigns low confidentiality impact, but specific confidentiality effects are not established. Private repository compromise and arbitrary host-level code execution are not demonstrated.

Mitigation

If you can’t patch tonight, do this now.

Until patching is complete, block unauthenticated access to /api/graphql through reverse-proxy or network controls, reduce public exposure, and disable public repository access where feasible. Preserve and inspect web, reverse-proxy, and application logs for suspicious GraphQL requests containing @gl_introduced. Correlate requests with repository deletions, unexpected project modifications, altered merge records, permission changes, and maintainer access restrictions. Verify repository and backup integrity; suspicious directive use alone indicates probing or attempted exploitation, not necessarily successful compromise.

Remediation

Patch, then assume compromise.

Immediately upgrade affected self-managed GitLab CE/EE installations to 18.11.11, 19.0.8, 19.1.6, 19.2.4, or a later supported release containing the fix. Installations on branches 18.2 through 18.10 must move to a patched branch. Follow standard backup and upgrade procedures. GitLab.com and GitLab Dedicated were remediated by GitLab and require no customer action. If unauthorized changes are detected, restore verified data from trusted backups and revoke affected credentials, access tokens, and deploy keys from a clean administrative environment.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-19478-PoCThis repository is a small standalone Python PoC for CVE-2026-19478 affecting GitLab GraphQL. It contains one executable script (poc.py), a README with usage and vulnerability details, and a license file. The exploit is not part of a larger framework. The script’s structure is straightforward: it defines affected version ranges, helper routines for parsing and comparing versions, an HTTP wrapper around requests, version detection logic, GraphQL query construction, and a main routine that selects a target and method based on CLI arguments. Version detection is best-effort and checks /api/v4/version when a PRIVATE-TOKEN is supplied, then falls back to scraping /help and /users/sign_in. Core exploit behavior: the PoC builds a GraphQL query against either project(fullPath: ...) or user(username: ...), then injects an attacker-chosen field name decorated with @gl_introduced(version: "999.0.0"). According to the repository, vulnerable GitLab versions create a fallback field and resolve it via object.public_send(), enabling arbitrary zero-argument method invocation on the underlying Project or User model. This allows safe verification with touch, state-changing actions such as deactivate/block/confirm/activate, and destructive actions such as destroy or delete. Operationally, the exploit supports modes check, modify, destroy, delete, and custom. The default benign check uses touch. Modify maps to deactivate for users and touch for projects. Destroy and delete are explicitly destructive and gated by an interactive confirmation prompt. The exploit expects public objects; if the project or user is not resolvable through GraphQL, the method will not be invoked. Overall, this is a real exploit PoC rather than a detector-only script. It includes both vulnerability assessment logic and active exploitation capability, with hardcoded but flexible method selection, making it OPERATIONAL rather than merely demonstrative.davkharrr · Disclosed Aug 18, 2026 · python · markdown · web · networkOperationalgitlab-cve-2026-19478-labRepository is a small self-contained GitLab vulnerability lab and PoC set with 5 files: a README, Docker Compose lab definition, two Python PoCs, and a Bash setup script. The main exploit file, poc_cve_2026_19478.py, targets CVE-2026-19478 in GitLab GraphQL. It sends POST requests to /api/graphql with attacker-controlled GraphQL fields annotated by @gl_introduced(version:"99.0.0") so that on vulnerable servers the fallback path resolves the field by calling object.public_send(field_name). In safe mode it probes with a harmless zero-argument method such as to_param against a public project and treats a non-null response as evidence of arbitrary method invocation. In optional proof mode, it first uses the authenticated REST API (/api/v4/projects) to create a disposable public project, then sends an unauthenticated GraphQL query requesting the destroy field to trigger Project#destroy, and finally verifies deletion via GET /api/v4/projects/{id}. This demonstrates unauthenticated destructive impact against public projects. The second PoC, poc_cve_2026_19650.py, is a safe detector for the sibling CVE-2026-19650. It submits a two-element Apollo-style GraphQL batch to /api/graphql and checks whether slot 0 incorrectly returns slot 1 data, indicating multiplex query/document swapping caused by shared tracer state. The repository also includes docker-compose.yml, which provisions two GitLab CE containers for A/B testing: vulnerable 19.2.2-ce.0 on port 8222 and patched 19.2.4-ce.0 on port 8224. setup.sh waits for GraphQL readiness, seeds a public project at root/pub, and creates an admin personal access token on each instance for lab use. Overall, this is a real exploit repository with both detection and optional impact-proof capability, focused on unauthenticated GraphQL abuse in GitLab rather than a generic scanner or framework module.dinosn · Disclosed Aug 18, 2026 · markdown · yaml · web · networkOperationalCVE-2026-19478This four-file repository contains a standalone Python exploit and a Dockerized vulnerable GitLab CE lab. gitlab_exploit.py is the primary entry point. It accepts a host/port or URL, defaults to http when no scheme is supplied, and performs all requests without Authorization or PRIVATE-TOKEN headers. In destructive mode it verifies an anonymously reachable public repository through GET /api/v4/projects/<repo>, posts a GraphQL query to /api/graphql using @gl_introduced(version:"99.0.0") and the field name destroy, then polls the REST API for a 404 response. Its --detect mode uses to_param rather than destroy, providing a non-destructive behavioral check. TLS certificate validation can be disabled with --insecure. The stated vulnerability is an unauthenticated GraphQL fallback/arbitrary zero-argument method invocation affecting GitLab Project objects; the implemented impact is deletion of a selected public project. The Python code does not enumerate projects, authenticate, establish persistence, or provide remote shell execution. The supplied query is basic and largely fixed apart from the project path, making this an operational PoC rather than a framework-integrated or weaponized exploit. Dockerfile builds from gitlab/gitlab-ce:19.2.2-ce.0, configures GitLab at localhost:80, exposes port 80, and starts seed.sh in the background. seed.sh waits for the local GraphQL service, then uses gitlab-rails runner to create/confirm a victim user and create the public victim/demo project. README.md documents Docker port publishing as host port 3000 to container port 80, claimed affected/fixed GitLab versions, and example invocation. The repository contains no original repository URL, git reference, or archive size in the supplied material.EQSTLab · Disclosed Aug 27, 2026 · python · bash · network · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitLabGitlabapplication
FAQ

Frequently asked questions

Is CVE-2026-19478 exploited in the wild?
Yes. As of Nov 12, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-19478?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-19478, the earliest disclosed Aug 18, 2026.
Is there a patch for CVE-2026-19478?
Immediately upgrade affected self-managed GitLab CE/EE installations to 18.11.11, 19.0.8, 19.1.6, 19.2.4, or a later supported release containing the fix. Installations on branches 18.2 through 18.10 must move to a patched branch.
What products are affected by CVE-2026-19478?
Gitlab.
How severe is CVE-2026-19478?
CVE-2026-19478 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 2.2% (82nd percentile) as of Nov 12, 2026.
Activity feed

Recent activity

210 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
malware newsNews · Nov 12, 2026Transcending the trust boundaries: how a cloud pentest works - Malware News - Malware Analysis, News and IndicatorsPresented as an example of a GitLab web-interface vulnerability enabling remote code execution within a managed-service runtime. The illustrative chain proceeds through discovery of a service account and access to resource-management services; the article does not establish observed exploitation.Read more ↗securelistNews · Nov 12, 2026Cloud pentesting: testing trust boundaries and tenant isolation | SecurelistReferenced as an illustrative GitLab web-interface vulnerability enabling remote code execution in a managed-service runtime. The article describes how this foothold could lead to service-account discovery and access to provider management services, but does not report an actual compromise involving this CVE.Read more ↗securelist ruNews · Nov 12, 2026Пентест облака: проверка границ доверия и изоляции тенантов | SecurelistPresented as an example of a GitLab web-interface vulnerability enabling remote code execution in a managed service. The illustrative attack chain proceeds to discovering an IAM service identity and accessing provider resource-management services. The article does not establish actual exploitation or independently substantiate the CVE's details.Read more ↗help net securityNews · Oct 13, 2026GitLab admins urged to patch critical RCE flaw (CVE-2026-97229) - Help Net SecurityA critical code injection vulnerability in GitLab allowing unauthenticated attackers to modify or delete public projects and user data. Mentioned as historical background; patches were released in August 2026.Read more ↗
+36 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity157Community discussion across Reddit, Mastodon, and other social sources.