GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an unauthenticated user to cause a denial of service due to insufficient resource throttling when processing merge request discussions.
CVE-2026-15975
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- 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
- 7.5
- EG Score
- 7.5(low)
- EG Risk
- 49(Track)EG Risk 49/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 29, 2026
Last Modified
July 29, 2026
Advisory Details (1)
Auto-updated Jul 29, 2026GitLab Patch Release: 19.2.1, 19.1.3, 19.0.5 | GitLab Docs
https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-1-released/Vendor Advisories for CVE-2026-15975(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 4× in last 7d / 4× 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-07-29 20:21 UTCEG score recompute
- 2026-07-29 20:01 UTCEG score recompute
- 2026-07-29 19:24 UTCEG score recompute
- 2026-07-29 19:22 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-15975?
When was CVE-2026-15975 disclosed?
What is the CVSS score of CVE-2026-15975?
How do I remediate CVE-2026-15975?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15975
Is Your Infrastructure Affected by CVE-2026-15975?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.