Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Clear
Network-reachable API abusable by an authenticated low-privileged user (PR:L) with no interaction; forged internal header crosses a trust boundary (S:C) yielding full admin impact.
Primary rating from Vendor (GoogleCloud).
CVSS VectorVendor: GoogleCloud
Lifecycle Timeline
3DescriptionCVE.org
Improper Privilege Management in Google SecOps (Chronicle SOAR) versions prior to 6.3.85 on Google Cloud Platform allows an authenticated attacker to escalate privileges to system-level administrative access using a crafted internal authentication header.
This vulnerability was patched with version 6.3.85, and no customer action is needed.
AnalysisAI
Privilege escalation in Google SecOps (Chronicle SOAR) versions prior to 6.3.85 on Google Cloud Platform allows an authenticated attacker to forge a crafted internal authentication header and elevate from a low-privileged account to system-level administrative access. The flaw stems from improper validation of the origin/trust of an internal auth header (CWE-346), and carries a critical CVSS 4.0 base score of 9.4 driven by high confidentiality, integrity, and availability impact plus a scope change onto subsequent systems. There is no public exploit identified at time of analysis; Google patched the cloud-hosted service transparently and states no customer action is needed.
Technical ContextAI
Google SecOps (formerly Chronicle SOAR) is Google Cloud's Security Orchestration, Automation and Response platform, delivered as a managed SaaS on GCP and used by SOC teams to run playbooks, case management, and integrations. The affected CPE is cpe:2.3:a:google_cloud:google_secops_(chronicle_soar). The root cause is classified as CWE-346 (Origin Validation Error): the application trusts an internal authentication header without adequately verifying that the header genuinely originated from a trusted internal component. Because the header is used to convey privilege/identity between internal services, a user who can craft or inject it can impersonate a system-level administrative principal, bypassing the intended authorization boundary between tenant/user roles and platform-administrative functions.
RemediationAI
Vendor-released patch: version 6.3.85. Because Google SecOps is a managed GCP service, Google deployed the fix to the hosted platform and explicitly states no customer action is needed - tenants are automatically on the patched build. Customers should verify their environment reflects version 6.3.85 or later and review the release notes at https://docs.cloud.google.com/chronicle/docs/soar/release-notes#May_23_2026. As standard hygiene given the flaw was a privilege-escalation path, teams may wish to review SOAR admin-account audit logs and role assignments for anomalous system-level access during the pre-patch window, though no compromise is indicated by the available data; there are no customer-side workarounds to apply since the vulnerable code path was in the vendor-operated backend.
More in Google Secops Chronicle Soar
View allSame weakness CWE-346 – Origin Validation Error
View allSame technique Privilege Escalation
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-53390
GHSA-54qh-3v8w-mm9c