GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute CI/CD pipelines on a protected branch without the required push permissions due to improper authorization in pipeline reference validation.
CVE-2026-15423
Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. a secondary CVSS source baseline 8.5; 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.5
- EG Score
- 8.5(high)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity85% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
August 12, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 12, 2026GitLab Patch Release: 19.2.2, 19.1.4, 19.0.6 | GitLab Docs
https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-2-released/Vendor Advisories for CVE-2026-15423(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 32× in last 7d / 37× 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-20 05:04 UTCEG score recompute
- 2026-08-20 05:04 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 16:47 UTCGHSA enrichment
- 2026-08-19 15:57 UTCGHSA enrichment
- 2026-08-19 03:28 UTCGHSA enrichment
- 2026-08-18 15:10 UTCEG score recompute
- 2026-08-18 15:10 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 07:32 UTCGHSA enrichment
- 2026-08-17 19:13 UTCEG score recompute
- 2026-08-17 19:13 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 05:44 UTCGHSA enrichment
- 2026-08-16 17:09 UTCEG score recompute
- 2026-08-16 17:09 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:52 UTCEG score recompute
- 2026-08-16 04:52 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 16:35 UTCGHSA enrichment
- 2026-08-15 04:18 UTCEG score recompute
- 2026-08-15 04:18 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 16:01 UTCGHSA enrichment
Show 12 moreShow fewer
- 2026-08-14 03:44 UTCEG score recompute
- 2026-08-14 03:44 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 15:27 UTCEG score recompute
- 2026-08-13 15:27 UTCGHSA enrichment
- 2026-08-13 15:15 UTCEG score recompute
- 2026-08-13 15:15 UTCGHSA enrichment
- 2026-08-13 06:35 UTCEG score recompute
- 2026-08-13 06:35 UTCGHSA enrichment
- 2026-08-12 18:18 UTCEG score recompute
- 2026-08-12 18:11 UTCEG score recompute
- 2026-08-12 18:11 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-15423?
When was CVE-2026-15423 disclosed?
Is CVE-2026-15423 actively exploited?
What is the CVSS score of CVE-2026-15423?
How do I remediate CVE-2026-15423?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15423
Is Your Infrastructure Affected by CVE-2026-15423?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.