GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.2 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that could have allowed an unauthenticated user to cause denial of service by sending specially crafted files to the container registry event endpoint under certain conditions.
CVE-2025-14511
HIGHPre-NVD 7.57.5—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-02-25. the CNA's CVSS baseline 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cna:gitlab, ghsa
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.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- 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
- 0%
- EPSS %ILE
- 28%
- KEV
- Not listed
Published
February 25, 2026
Last Modified
June 17, 2026
References (3)
Vendor Advisories for CVE-2025-14511(1)
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 3× in last 7d / 3× 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-27 14:12 UTCEPSS rescore
- 2026-07-27 12:55 UTCEG score recompute
- 2026-07-27 12:55 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2025-14511?
CVE-2025-14511 is a high vulnerability published on February 25, 2026. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.2 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that could have allowed an unauthenticated user to cause denial of service by sending specially crafted files to the container registry event endpoint under…
When was CVE-2025-14511 disclosed?
CVE-2025-14511 was first published in the National Vulnerability Database on February 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-14511 actively exploited?
CVE-2025-14511 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 72.5% of all scored CVEs.
What is the CVSS score of CVE-2025-14511?
CVE-2025-14511 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-14511?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-14511, 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-2025-14511
Is Your Infrastructure Affected by CVE-2025-14511?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.