CVE-2026-19478

CRITICALPre-NVD 9.49.4
EchelonGraph scoreHIGH confidence

Score 9.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-17. a secondary CVSS source baseline 9.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4 that under certain conditions could allow an unauthenticated user to remotely modify or delete public projects and user data via a GraphQL directive.

CVSS v3
9.4
EG Score
9.4(high)
EG Risk
73(Track)
EG Risk 73/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity94% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

August 17, 2026

Last Modified

August 18, 2026

Advisory Details (1)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

GitLab Critical Patch Release: 19.2.4, 19.1.6, 19.0.8, 18.11.11 | GitLab Docs

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-4-released/

Vendor Advisories for CVE-2026-19478(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 03:56 UTCGHSA enrichment
  2. 2026-08-19 23:51 UTCGHSA enrichment
  3. 2026-08-19 19:46 UTCEG score recompute
  4. 2026-08-19 19:46 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-19 15:41 UTCGHSA enrichment
  7. 2026-08-19 11:37 UTCGHSA enrichment
  8. 2026-08-19 07:31 UTCGHSA enrichment
  9. 2026-08-19 03:24 UTCGHSA enrichment
  10. 2026-08-18 23:19 UTCGHSA enrichment
  11. 2026-08-18 19:14 UTCGHSA enrichment
  12. 2026-08-18 15:09 UTCGHSA enrichment
  13. 2026-08-18 14:54 UTCEG score recompute
  14. 2026-08-18 14:54 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 09:46 UTCGHSA enrichment
  17. 2026-08-18 05:41 UTCGHSA enrichment
  18. 2026-08-18 01:36 UTCGHSA enrichment
  19. 2026-08-17 21:32 UTCEG score recompute
  20. 2026-08-17 21:31 UTCGHSA enrichment
  21. 2026-08-17 20:55 UTCEG score recompute
  22. 2026-08-17 20:29 UTCEG score recompute
  23. 2026-08-17 20:11 UTCEG score recompute
  24. 2026-08-17 20:09 UTCMITRE cvelistV5first tracked

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCdavkharrr/CVE-2026-19478-PoC
    First seen Aug 18, 2026

    CVE-2026-19478 PoC . Unauthenticated remote code-injection in GitLab's GraphQL layer

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-19478.yaml
    First seen Jan 1, 2026

    GitLab CE/EE - GraphQL @gl_introduced Arbitrary Method Invocation

    Open source ↗

Frequently asked(5)

What is CVE-2026-19478?
CVE-2026-19478 is a critical vulnerability published on August 17, 2026. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4 that under certain conditions could allow an unauthenticated user to remotely modify or delete public projects and user data via a GraphQL…
When was CVE-2026-19478 disclosed?
CVE-2026-19478 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19478 actively exploited?
CVE-2026-19478 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.0% of all scored CVEs.
What is the CVSS score of CVE-2026-19478?
CVE-2026-19478 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-19478?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19478, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-19478

Explore →

Is Your Infrastructure Affected by CVE-2026-19478?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.