HomeIntelligenceBrief
VULNERABILITY BRIEF🔴 Critical Vulnerability

Critical Unauthenticated GraphQL Vulnerability in GitLab (CVE‑2026‑19478) Allows Remote Project Modification/Deletion

GitLab disclosed CVE‑2026‑19478, a critical unauthenticated flaw that lets attackers modify or delete public projects on self‑managed servers. The issue underscores the need for continuous patch monitoring and control mapping to satisfy SOC 2 audit requirements.

LiveThreat™ Intelligence · 📅 August 18, 2026· 📰 securityaffairs.com
🔴
Severity
Critical
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
Actions
3 recommended
📰
Source
securityaffairs.com

Critical Unauthenticated GraphQL Vulnerability in GitLab (CVE‑2026‑19478) Allows Remote Project Modification/Deletion

What It Is — GitLab disclosed a critical flaw (CVE‑2026‑19478) in its GraphQL API that permits an unauthenticated attacker to modify or delete public projects on self‑managed installations. The vulnerability carries a CVSS 9.4 score. A secondary CVE‑2026‑19650 (CVSS 7.1) adds a CSRF issue in multiplex queries.

Exploitability — No public exploits have been observed, and no proof‑of‑concept code is available. The flaw is “remote‑code‑execution‑like” in that it requires no credentials or user interaction, making it trivially exploitable once a vulnerable version is reachable.

Affected Products — GitLab self‑managed (self‑hosted) servers on versions prior to 19.2.4, 19.1.6, 19.0.8, and 18.11.11. Branches 18.2‑18.10 are not receiving a fix and must be upgraded to a supported branch.

Why It Matters for Compliance & Audit Readiness

  • Control Mapping – The flaw highlights gaps in your Change Management (SOC 2 CC6.1) and Configuration Management (CC6.2) controls; continuous evidence of patch deployment is essential to demonstrate due diligence.
  • Audit Trail – Maintaining verifiable records of version upgrades and remediation actions provides defensible audit evidence for SOC 2 examinations and for customers demanding a trusted supply‑chain posture.
  • Enterprise Buyer Expectations – Large buyers now require proof that SaaS/tooling environments are patched promptly; a missing patch can become a deal‑breaker in security reviews.

Recommended Actions

  • Verify your GitLab version and upgrade immediately to the patched releases (19.2.4, 19.1.6, 19.0.8, or 18.11.11).
  • For installations on 18.2‑18.10, plan a migration to a supported branch; the current line will not receive a fix.
  • Capture upgrade logs and hash the binaries as immutable evidence for SOC 2 control testing.
  • Integrate automated vulnerability scanning and patch‑validation into your CI/CD pipeline to ensure continuous compliance.

Source: Security Affairs – GitLab patches critical unauthenticated GraphQL vulnerability

📰 Original Source
https://securityaffairs.com/197454/hacking/gitlab-patches-critical-unauthenticated-graphql-vulnerability.html

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Every gap like this maps to a control you can evidence.

The Verisq AI Trust Operations platform maps incidents to your control framework and collects the evidence continuously — so your Trust Center shows proof, not promises, when a buyer or auditor asks.

Explore the Verisq AI Trust Operations platform →