Security readout for executives and security teams
Plain-English summary
An authenticated Chronicle SOAR user could abuse a crafted internal authentication header to obtain system-level administrator privileges. That access could expose or alter sensitive security operations data and disrupt service. Google reports the issue was fixed in version 6.3.85 and says customers need take no action.
Executive priority
Treat this as urgent assurance rather than emergency customer patching. Confirm Google's managed update reached the environment and review historical administrative activity from the pre-fix period. The potential impact is severe, but the supplied evidence does not establish exploitation, and Google says customers need take no remediation action.
Technical view
Google SecOps (Chronicle SOAR) on Google Cloud Platform before 6.3.85 improperly handled an internal authentication header, allowing a low-privileged authenticated remote attacker to gain system-level administrative access without user interaction. The CVSS 4.0 score is 9.4, with high confidentiality, integrity, and availability impacts. The record associates the issue with CWE-346.
Likely exposure
Exposure is limited to Google SecOps (Chronicle SOAR) on Google Cloud Platform running versions before 6.3.85. The supplied record identifies no other products or deployment models. Google states the service was patched and no customer action is required, but organizations may still need assurance that their tenant received the update.
Exploitation context
The supplied record is not marked as KEV and provides no evidence of active exploitation or public exploit availability. Exploitation requires network access and an authenticated low-privileged account, but no user interaction. The crafted header and affected internal component are not publicly detailed in the bundle.
Researcher notes
Public information does not identify the header name, affected component, detection indicators, or observed attacks. Do not infer that on-premises deployments or other Google products are affected. Validation should focus on version assurance, authenticated privilege boundaries, and historical audit evidence without attempting exploitation.
Mitigation direction
- Rely on Google's 6.3.85 service update; the vendor states no customer action is required.
- Check current Google release guidance for any revised remediation or monitoring recommendations.
- Escalate to Google Cloud support if tenant patch status cannot be confirmed.
- Preserve relevant authentication, privilege-change, and administrative audit records for review.
Validation and detection
- Confirm through vendor-supported visibility that the tenant is running version 6.3.85 or later.
- Review pre-fix audit history for unexpected privilege elevation or system-level administrative activity.
- Identify low-privileged accounts active before remediation and investigate anomalous administrative changes.
- Verify that no unsupported or separately managed Chronicle SOAR instance remains below 6.3.85.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-346: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-15587 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——GoogleCloudVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://docs.cloud.google.com/chronicle/docs/soar/release-notes#May_23_2026CVE reference, GoogleCloud
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Origin Validation Error
Origin Validation Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.