CVE-2026-15975

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-29. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 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 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.

CVSS v3
7.5
EG Score
7.5(high)
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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 29, 2026
No patch confirmed yet.
generic

GitLab 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 11× in last 7d / 11× 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-07-31 12:23 UTCGHSA enrichment
  2. 2026-07-31 01:31 UTCEG score recompute
  3. 2026-07-31 01:30 UTCGHSA enrichment
  4. 2026-07-30 14:38 UTCEG score recompute
  5. 2026-07-30 14:38 UTCGHSA enrichment
  6. 2026-07-30 07:25 UTCEG score recompute
  7. 2026-07-30 07:25 UTCGHSA enrichment
  8. 2026-07-29 20:21 UTCEG score recompute
  9. 2026-07-29 20:01 UTCEG score recompute
  10. 2026-07-29 19:24 UTCEG score recompute
  11. 2026-07-29 19:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15975?
CVE-2026-15975 is a high vulnerability published on July 29, 2026. 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…
When was CVE-2026-15975 disclosed?
CVE-2026-15975 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15975 actively exploited?
CVE-2026-15975 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.8% of all scored CVEs.
What is the CVSS score of CVE-2026-15975?
CVE-2026-15975 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-15975?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15975, 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-15975

Explore →

Is Your Infrastructure Affected by CVE-2026-15975?

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

Start Free Scan →Browse All CVEs