CVE-2026-15623

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. 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: epss, secondary
Trending — 4 sources updated this week
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A SQL Injection vulnerability in a legacy dashboard widget API in Google Cloud Google SecOps (Chronicle SOAR) versions prior to 6.3.85 on Google Cloud Platform allows an authenticated attacker to execute blind SQL queries using a crafted request parameter.

This vulnerability was patched in version 6.3.85, and no customer action is needed.

CVSS v3
9.4
EG Score
9.4(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity94% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

August 17, 2026

Last Modified

August 17, 2026

Advisory Details (1)

Auto-updated Aug 17, 2026
Patch available.
generic Patch Available

Google Security Operations SOAR release notes  |  Google Cloud Documentation

https://docs.cloud.google.com/chronicle/docs/soar/release-notes#May_23_2026

Vendor Advisories for CVE-2026-15623(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 36× in last 7d / 36× 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-21 07:23 UTCGHSA enrichment
  2. 2026-08-21 03:17 UTCGHSA enrichment
  3. 2026-08-20 23:08 UTCEG score recompute
  4. 2026-08-20 23:08 UTCGHSA enrichment
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 19:02 UTCGHSA enrichment
  7. 2026-08-20 14:56 UTCGHSA enrichment
  8. 2026-08-20 10:50 UTCGHSA enrichment
  9. 2026-08-20 06:44 UTCGHSA enrichment
  10. 2026-08-20 02:37 UTCGHSA enrichment
  11. 2026-08-19 22:27 UTCGHSA enrichment
  12. 2026-08-19 18:20 UTCEG score recompute
  13. 2026-08-19 18:20 UTCGHSA enrichment
  14. 2026-08-19 17:03 UTCEPSS rescore
  15. 2026-08-19 14:06 UTCGHSA enrichment
  16. 2026-08-19 09:59 UTCGHSA enrichment
  17. 2026-08-19 05:51 UTCGHSA enrichment
  18. 2026-08-19 01:44 UTCGHSA enrichment
  19. 2026-08-18 21:37 UTCGHSA enrichment
  20. 2026-08-18 17:09 UTCEG score recompute
  21. 2026-08-18 17:09 UTCGHSA enrichment
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-18 13:00 UTCGHSA enrichment
  24. 2026-08-18 08:51 UTCGHSA enrichment
  25. 2026-08-18 04:45 UTCGHSA enrichment
Show 11 more
  1. 2026-08-18 00:39 UTCGHSA enrichment
  2. 2026-08-17 20:31 UTCGHSA enrichment
  3. 2026-08-17 16:23 UTCEG score recompute
  4. 2026-08-17 16:23 UTCGHSA enrichment
  5. 2026-08-17 15:34 UTCEG score recompute
  6. 2026-08-17 15:34 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 11:28 UTCGHSA enrichment
  9. 2026-08-17 07:22 UTCEG score recompute
  10. 2026-08-17 06:42 UTCEG score recompute
  11. 2026-08-17 06:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15623?
CVE-2026-15623 is a critical vulnerability published on August 17, 2026. A SQL Injection vulnerability in a legacy dashboard widget API in Google Cloud Google SecOps (Chronicle SOAR) versions prior to 6.3.85 on Google Cloud Platform allows an authenticated attacker to execute blind SQL queries using a crafted request parameter. This vulnerability was patched in version…
When was CVE-2026-15623 disclosed?
CVE-2026-15623 was first published in the National Vulnerability Database on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15623 actively exploited?
CVE-2026-15623 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 89.4% of all scored CVEs.
What is the CVSS score of CVE-2026-15623?
CVE-2026-15623 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-15623?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15623, 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-15623

Explore →

Is Your Infrastructure Affected by CVE-2026-15623?

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