GCP-2026-015
Source GCP Compute Engine Security
Not known to be exploited.
Data as of 26 Oct 2026, 22:13 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
Public on cve.org; its publication date is not in this record
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Upgrade Container-Optimized OS nodes to cos-125-19216-220-57, which contains the fix for CVE-2026-23268. If managing COS VMs directly, recreate VMs using the updated images as per the official instructions. For users of managed services such as GKE, Dataflow, or Cloud SQL that use COS, follow the specific upgrade instructions provided for those services. Fixes for COS milestones 117 and 121 are still in progress; monitor official channels for updates.
Description
A vulnerability identified as CVE-2026-23268, known as CrackArmor, exists in the Linux kernel's AppArmor component on Container-Optimized OS (COS) nodes. This flaw allows unprivileged users to bypass kernel protections, escalate privileges to root, and break local container isolation. The vulnerability is rated high severity. Google recommends upgrading COS nodes to version cos-125-19216-220-57, which contains the fix. For managed services using COS, users should follow the respective upgrade instructions. Fixes for earlier COS milestones 117 and 121 are in progress.