Skip to content
major vulnerability· requires attention

Affects Google Cloud Shell (GCP) — a widely used cloud management tool; OAuth token theft can enable broad account/API compromise.

Cloud

CVE-2026-85267

8.7
High
EPSS n/aPatch availableOct 20, 2026

Cloud Shell WebSocket hijack enables OAuth token theft (patched).

common questions

Is CVE-2026-85267 being exploited?

Not confirmed. CVE-2026-85267 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-85267?

CVE-2026-85267 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-85267?

Yes. A fix has been recorded for CVE-2026-85267. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-85267 affect?

CVE-2026-85267 affects Google Cloud Shell (GCP) - versions prior to 2026-07-22. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-85267?

Verify Cloud Shell updated; rotate affected OAuth tokens if suspicious.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Google Cloud Shell (GCP) - versions prior to 2026-07-22
impact

Cross-origin WebSocket hijack of active Cloud Shell sessions to exfiltrate OAuth access tokens, enabling unauthorized API/cloud access.

action required

Monitor only

affected versions
Google Cloud Cloud Shell
  • affected< 2026-07-22

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free