CVE-2026-15217

HIGHPre-NVD 8.78.7—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: 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 18.2 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed cross-site scripting due to improper neutralization of user-controlled values rendered in table cell content by an analytics dashboard component.

CVSS v3
8.7
EG Score
8.7(high)
EG Risk
39(Track)
EG Risk 39/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
Severity87% × 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, 2026
No patch confirmed yet.
generic

GitLab 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/
generic

GitLab.org / GitLab · GitLab

https://gitlab.com/gitlab-org/gitlab/-/work_items/605449

Vendor Advisories for CVE-2026-15217(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 33× in last 7d / 38× 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-08-20 03:48 UTCEG score recompute
  2. 2026-08-20 03:48 UTCGHSA enrichment
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-19 16:46 UTCGHSA enrichment
  5. 2026-08-19 13:09 UTCGHSA enrichment
  6. 2026-08-19 02:09 UTCGHSA enrichment
  7. 2026-08-18 15:09 UTCEG score recompute
  8. 2026-08-18 15:09 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 06:14 UTCGHSA enrichment
  11. 2026-08-17 19:13 UTCEG score recompute
  12. 2026-08-17 19:13 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 07:29 UTCGHSA enrichment
  15. 2026-08-16 20:29 UTCEG score recompute
  16. 2026-08-16 20:29 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 09:29 UTCEG score recompute
  19. 2026-08-16 09:29 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 22:29 UTCGHSA enrichment
  22. 2026-08-15 11:29 UTCEG score recompute
  23. 2026-08-15 11:29 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-15 00:29 UTCGHSA enrichment
Show 13 more
  1. 2026-08-14 13:28 UTCGHSA enrichment
  2. 2026-08-14 02:27 UTCEG score recompute
  3. 2026-08-14 02:27 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 15:27 UTCEG score recompute
  6. 2026-08-13 15:27 UTCGHSA enrichment
  7. 2026-08-13 15:15 UTCEG score recompute
  8. 2026-08-13 15:15 UTCGHSA enrichment
  9. 2026-08-13 07:24 UTCEG score recompute
  10. 2026-08-13 07:23 UTCGHSA enrichment
  11. 2026-08-12 20:20 UTCEG score recompute
  12. 2026-08-12 19:21 UTCEG score recompute
  13. 2026-08-12 19:20 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15217?
CVE-2026-15217 is a high vulnerability published on August 12, 2026. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed cross-site scripting due to improper neutralization of user-controlled values rendered in table cell content by…
When was CVE-2026-15217 disclosed?
CVE-2026-15217 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15217 actively exploited?
CVE-2026-15217 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 82.0% of all scored CVEs.
What is the CVSS score of CVE-2026-15217?
CVE-2026-15217 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-15217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15217, 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-15217

Explore →

Is Your Infrastructure Affected by CVE-2026-15217?

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

Start Free Scan →Browse All CVEs