GitLab has remediated an issue in GitLab EE affecting all versions from 18.9 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with developer-role permissions could have executed arbitrary commands in a CI context, due to the Claude agent processing configuration from a user-controlled source.
CVE-2026-18252
HIGHPre-NVD 7.37.3
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.3 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).
Triggered by: NVD CVSS baseline
Sources: secondary
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.3Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(low)
- EG Risk
- 33(Track)EG Risk 33/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 computedSeverity73% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 26, 2026
Advisory Details (2)
Auto-updated Aug 26, 2026No patch confirmed yet.
generic
GitLab Patch Release: 19.3.1, 19.2.5, 19.1.7 | GitLab Docs
https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-1-released/Vendor Advisories for CVE-2026-18252(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-08-26 16:21 UTCEG score recompute
- 2026-08-26 15:50 UTCEG score recompute
- 2026-08-26 13:43 UTCEG score recompute
- 2026-08-26 13:42 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-829
- CVE-2021-41037EG 10.0CRITICAL
- CVE-2022-1161EG 10.0EPSS p92CRITICAL
- CVE-2020-4561EG 10.0CRITICAL
- CVE-2022-24119EG 9.8CRITICAL
- CVE-2020-16152EG 9.8EPSS p98CRITICAL
- CVE-2021-21804EG 9.8CRITICAL
- CVE-2020-25414EG 9.8CRITICAL
- CVE-2020-3794EG 9.8EPSS p94CRITICAL
- CVE-2020-8128EG 9.8CRITICAL
- CVE-2012-4919EG 9.8CRITICAL
Frequently asked(4)
What is CVE-2026-18252?
CVE-2026-18252 is a high vulnerability published on August 26, 2026. GitLab has remediated an issue in GitLab EE affecting all versions from 18.9 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with developer-role permissions could have executed arbitrary commands in a CI context, due to the Claude…
When was CVE-2026-18252 disclosed?
CVE-2026-18252 was first published in the National Vulnerability Database on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-18252?
CVE-2026-18252 has a CVSS v3 base score of 7.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-18252?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18252, 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-18252
Is Your Infrastructure Affected by CVE-2026-18252?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.