Google’s November 18 update to bulletin GCP-2026-078 adds 1.37.2-gke.1325000 as a fixed version for Container-Optimized OS node pools. The bulletin originally appeared November 4 and concerns Linux kernel flaw CVE-2026-98432.
Google says an unprivileged container process can trigger a kernel panic or escape to execute code as root on the node. A separate network route requires access to a TCP listener on a node, pod or control-plane IP endpoint. Both GKE Standard and Autopilot are affected.
Other listed Container-Optimized OS fixes are 1.36.5-gke.1982000, 1.35.9-gke.1505000, 1.34.12-gke.1539000, 1.33.13-gke.2207000 and 1.32.13-gke.2906000, or later applicable patch versions. Ubuntu node-image patches remain in progress in the reviewed bulletin.
An available patch may precede the channel default
Google’s release-channel documentation permits eligible patch versions from a newer channel when the same minor version is available in the cluster’s enrolled channel. The documented route uses the GKE API or gcloud CLI; administrators should check the conditions for their cluster before planning the change.
IPCRIME analysis: verify nodes and workload boundaries
For operations teams, the immediate task is to compare the bulletin with the real node-image family and running version in every pool. Record the control-plane version separately. An upgrade plan should account for mixed pools and replacement nodes, so a completed change on one pool is not mistaken for completion across the cluster.
Assess who can submit workloads and which services can reach cluster endpoints. Network restrictions are useful containment, but a local container path changes the review: workloads already admitted to the cluster must also be considered. A firewall change alone should not be recorded as resolving the full vulnerability.
Before maintenance, confirm that important workloads can tolerate node replacement and that capacity is available for the planned rollout. Afterward, verify the version on the replacement nodes, workload health and the remaining exceptions. Keep Ubuntu pools on an explicit follow-up list until Google publishes their applicable fix.
This is a newly documented remediation option for an existing vulnerability. The update should drive a concrete version check and maintenance decision; it does not establish that exploitation has occurred in any particular customer cluster.
Related reading: kube-bench: Kubernetes cluster security benchmark checks — Digital Arsenal.
Featured image: conceptual IPCRIME artwork, not a photograph or screenshot of this incident or product.
