Skip to main content

Google SecOps EUVDEUVD-2026-60060

| CVE-2026-15623 CRITICAL
SQL Injection (CWE-89)
2026-08-17 GoogleCloud GHSA-8f9j-vmpc-422v
9.4
CVSS 4.0 · Vendor: GoogleCloud
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to SecOps tenant
  2. Delivery
    Reach legacy dashboard widget API
  3. Exploit
    Inject crafted SQL parameter
  4. Execution
    Blind boolean/time-based inference
  5. Impact
    Exfiltrate database contents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a valid authenticated Google SecOps (Chronicle SOAR) account (CVSS PR:L) and access to the legacy dashboard widget API endpoint; exploitation is performed by supplying a crafted request parameter that is injected into a blind SQL query. Limiting factors: the attacker must already be an authenticated tenant user (there is no unauthenticated path), the vulnerable code path is the specific legacy dashboard widget API rather than the whole product, and only versions prior to 6.3.85 are affected - the vendor-managed SaaS has already been upgraded, closing the window for customers.

Impact

The CVSS 4.0 score of 9.4 reflects a network-reachable, low-complexity attack requiring only low privileges (PR:L) and no user interaction, with High confidentiality, integrity and availability impact on both the vulnerable and subsequent systems (VC/VI/VA:H, SC/SI/SA:H). The subsequent-system High ratings imply the database access could pivot beyond the immediate widget context, which is plausible for a SOAR platform holding cross-integration case data and secrets. However, exploitation is gated by valid authenticated access (PR:L), which meaningfully narrows the attacker pool to existing tenant users. No EPSS score, no KEV listing and no POC are present in the provided data, so real-world exploitation pressure is currently unproven - the high rating is driven by potential impact, not observed attacks. Because the environment is vendor-managed SaaS already patched at 6.3.85 with no customer action needed, residual real-world risk to customers is low despite the critical score.

Exploit ScenarioDerived

An attacker who already holds a valid low-privileged Google SecOps tenant account sends a crafted parameter to the legacy dashboard widget API, injecting boolean or time-based SQL to blindly extract case data, integration secrets or other tenant records from the backend database. No public exploit code is identified, and the network/low-complexity vector means such requests could be automated once a foothold account exists.

Monitor Track and reassess. Why: Vendor states no customer action required.
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 17, 2026

Blind SQL injection in Google SecOps (Chronicle SOAR) versions before 6.3.85 lets an authenticated user abuse a crafted request parameter in a legacy dashboard widget API to run arbitrary blind SQL queries against the backend database. CVSS 4.0 rates it 9.4 (critical) with a low-privilege network vector; no public exploit is identified at time of analysis and it is not listed in CISA KEV. Because the platform is a Google Cloud-managed SaaS, the fix was deployed by the vendor and no customer action is required.

RemediationAI

Vendor-released patch: 6.3.85. Because Google SecOps is a Google Cloud-managed SaaS platform, Google states the fix was applied server-side and no customer action is needed; customers should simply confirm their tenant is running 6.3.85 or later via the release notes at https://docs.cloud.google.com/chronicle/docs/soar/release-notes#May_23_2026. As defense-in-depth for the pre-patch exposure window, tighten SOAR account provisioning and review who holds authenticated tenant access, since exploitation requires a valid low-privileged account; audit dashboard widget API access logs for anomalous or time-based query patterns and rotate any credentials suspected of misuse. No customer-side configuration workaround is applicable given the hosted delivery model.

Affected VersionsENISA

Google SecOps (Chronicle SOAR) 0 <6.3.85

Affected Packages

euvd google_secops_chronicle_soar fix: 6.3.85

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Google SecOps (formerly Chronicle SOAR, originally Siemplify) is Google Cloud's security orchestration, automation and response platform used by SOC teams to run playbooks, manage cases and build dashboards. The flaw is a classic CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) in a legacy dashboard widget API endpoint, where a request parameter is concatenated into a SQL statement without proper parameterization. The 'blind' nature means query results are not returned directly in the HTTP response; an attacker instead infers data via boolean or time-based inference. The single CPE, cpe:2.3:a:google_cloud:google_secops_(chronicle_soar), confirms the affected component is the hosted SaaS application layer rather than an on-prem library shipped to customers.

Know when Google Secops Chronicle Soar gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GoogleCloud) PRIMARY 9.4 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/U:Clear
vuln.today AI 8.3 HIGH

Network-reachable authenticated endpoint gives AV:N/AC:L/PR:L; blind SQLi yields full DB read/write (C:H/I:H) with limited direct availability impact (A:L).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (GoogleCloud).

CVSS VectorVendor: GoogleCloud

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

Lifecycle Timeline

2
CVE Published
Aug 17, 2026 - 12:38 cve.org
CRITICAL 9.4
Patch available
Aug 17, 2026 - 07:16 EUVD

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Google SecOps (Chronicle SOAR) contained a critical blind SQL injection vulnerability (CVE-2026-15623, CVSS 9.4) enabling authenticated users to execute arbitrary queries against the backend database, potentially exposing or modifying sensitive security event data. Google has automatically deployed the required patch (version 6.3.85) to all cloud instances, eliminating the vulnerability, but organizations should verify deployment and audit user access controls.

Business Impact: High
Compensating Controls

Vendor patch deployed automatically (version 6.3.85); implement multi-factor authentication for all user accounts, role-based access controls restricting administrative privileges, and continuous monitoring of database access patterns with real-time alerting.

Threat Intelligence Overview

EPSS Score
0.2%
Top 89% exploitable
Prevalence
Medium
enterprise SOAR platform used by SOC teams, not universally deployed
Service Type
Hosted
Vendor-managed, no client patch needed
Social Media
4
Sightings
Data Quality
7 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
Vendor states no customer action required
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

47
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +47
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy