Cross-Site WebSocket Hijacking Enables Session Takeover in Google Cloud Cloud Shell

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-85267?

CVE-2026-85267 is a vulnerability classified as Missing Origin Validation in WebSockets, affecting Cloud Shell (affected versions: < 2026-07-22). This vulnerability is rated High, with a CVSS score of 8.7. Current sources do not report this vulnerability as exploited.

Overview

Original source data

A Cross-Site WebSocket Hijacking vulnerability in Cloud Shell prior to 2026-07-22 on Google Cloud Platform allows an unauthenticated attacker to hijack an active Cloud Shell session and exfiltrate the user's OAuth access token using a cross-origin WebSocket request. This vulnerability was patched on 22 July 2026, and no customer action is needed.

Affected products and scope

  • Google Cloud Cloud Shell: Affected before 2026-07-22. The structured affected data uses a date-based version type with version: 0, versionType: date, and lessThan: 2026-07-22.
  • The record sets the default status to unaffected outside the stated affected interval. Google Cloud describes a service-side remediation, and no separately installed customer version or customer upgrade release is provided.

Technical details

This is a CWE-1385 Missing Origin Validation in WebSockets vulnerability in Cloud Shell. Missing validation of the Origin header during WebSocket upgrades allowed an unauthenticated attacker to send a cross-origin WebSocket request that could hijack an active Cloud Shell session and exfiltrate the user's OAuth access token. The recorded preconditions are network reachability, no required privileges, low attack complexity, and passive user interaction. Google Cloud's release note says the remediation tightened Origin validation on WebSocket upgrades and added an allowed port list for TCP and SSH tunnels. The record does not disclose the specific endpoint, handshake sequence, token transport, or remaining internal implementation details.

Exploitability

  • Reachability: The attack can be delivered over the network through a cross-origin WebSocket request.
  • Authentication: The attacker does not need authentication or prior privileges.
  • User condition: An active Cloud Shell session and passive user interaction are required according to the record.
  • Exploitation status: The record sets public_exploit to false, while known_exploited is null. No public exploit is recorded, but observed exploitation status is not established.

Technical impact

The vulnerability allowed an unauthenticated attacker to hijack an active Cloud Shell session through a cross-origin WebSocket request and exfiltrate the user's OAuth access token. The direct technical outcome is loss of session control and exposure of session credentials. Subsequent token use could enable actions within the token's authorization scope, but that outcome depends on the token's scope, validity, and state and is not confirmed for every deployment. The record does not identify a specific data disclosure, resource modification, or service outage.

Business impact

  • An attacker could take control of an active Cloud Shell session, creating a risk of unauthorized operations performed through that session.
  • The user's OAuth access token could be exposed. If still valid, the token might permit actions within its authorization scope, although the record does not identify the specific resources that would be reachable.
  • Unauthorized session control or token use could affect the confidentiality, integrity, and availability of activities performed through Cloud Shell.
  • The record provides no evidence of a specific affected customer, disclosed dataset, or confirmed account compromise.

Remediation

  1. No customer-side patching is required: Google Cloud states that the vulnerability was remediated service-side on July 22, 2026, with no customer action required.
  2. Treat Cloud Shell sessions active before 2026-07-22 as falling within the affected time window when performing historical exposure assessment.
  3. If unusual OAuth access token use is found in connection with sessions from the affected period, follow the organization's existing token and account incident-response procedures. The record does not prescribe token revocation or rotation for every customer.
  4. Do not infer the status of other branches or releases beyond the confirmed date boundary.

Detection

  1. Inventory Cloud Shell use before 2026-07-22, because the affected boundary is defined by a service date rather than by a customer-installed software version.
  2. Confirm through current service records or operational documentation that Cloud Shell has the stricter Origin validation for WebSocket upgrades and the allowed port list for TCP and SSH tunnels described by Google Cloud.
  3. If identity or audit telemetry is available, review unusual OAuth access token use and related Cloud Shell activity for sessions in the pre-remediation period. This is a precautionary review, not a confirmed indicator.
  4. The record provides no product-specific log signature or IOC. The absence of suspicious log evidence does not prove that a session or token was not affected.
Sources (10)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.