GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.3 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an authenticated user could have induced a targeted user to perform unintended state-changing HTTP requests due to improper sanitization of user-controlled data in the Markdown JSON table renderer.
CVE-2026-78252
Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. a secondary CVSS source baseline 8.2; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(high)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity82% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 33%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 16, 2026
Advisory Details (2)
Auto-updated Sep 16, 2026GitLab Critical Patch Release: 19.3.2, 19.2.6, 19.1.8 | GitLab Docs
https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/Work items · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/work_items/621447Vendor Advisories for CVE-2026-78252(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 16× in last 7d / 16× 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.
- 2026-09-18 19:31 UTCEG score recompute
- 2026-09-18 19:31 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 07:32 UTCGHSA enrichment
- 2026-09-17 19:33 UTCEG score recompute
- 2026-09-17 19:33 UTCGHSA enrichment
- 2026-09-17 07:33 UTCGHSA enrichment
- 2026-09-16 19:33 UTCGHSA enrichment
- 2026-09-16 16:39 UTCEG score recompute
- 2026-09-16 16:38 UTCGHSA enrichment
- 2026-09-16 15:50 UTCEG score recompute
- 2026-09-16 15:50 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 07:19 UTCEG score recompute
- 2026-09-16 06:37 UTCEG score recompute
- 2026-09-16 06:37 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-78252?
When was CVE-2026-78252 disclosed?
Is CVE-2026-78252 actively exploited?
What is the CVSS score of CVE-2026-78252?
How do I remediate CVE-2026-78252?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78252
Is Your Infrastructure Affected by CVE-2026-78252?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.