GCP News - 2026-05-11
2026-05-11
最終更新: 2026-08-27 21:31:34 JST
GKE Security Bulletins
GCP-2026-030
- Link: https://docs.cloud.google.com/kubernetes-engine/security-bulletins#gcp-2026-030
- Published: 2026-05-11 09:00:00
- Fetched: 2026-08-27 21:31:34
詳細を表示
Published: 2026-05-11
Updated: 2026-06-24
Reference: CVE-2026-43284, CVE-2026-43500
2026-06-24 Update: Added patch versions for GKE.
2026-05-20 Update: Added CVE-2026-43500 and added CVE IDs to exploit paths.
GKE
Updated: 2026-06-24
| Description | Severity |
|---|---|
|
Container breakout vulnerabilities CVE-2026-43284 and CVE-2026-43500 have been found in the Linux kernel, known as DirtyFrag. They allow an unprivileged local attacker to escalate to root on the host. There are two exploit paths. rxrpc exploit path (CVE-2026-43500): Container-Optimized OS is not vulnerable because the vulnerable module is not compiled in. Ubuntu nodes are vulnerable. esp4 exploit path (CVE-2026-43284): Both Container-Optimized OS and Ubuntu are vulnerable, but the GKE default seccomp profile provides a mitigation that protects all Autopilot clusters and Standard clusters with Autopilot-managed node pools. The esp4 exploit path requires the user to have the ability to make the unshare syscall to obtain CAP_NET_ADMIN. Containers that use the Containers using GKE Sandbox are not impacted. What should I do?2026-06-24 Update: The following versions of GKE are updated with code to fix this vulnerability on Container-Optimized OS. Upgrade your Container-Optimized OS node pools to the following versions or later:
Upstream kernel patches have only recently been released. Those patches are being built into GKE releases and this bulletin will be updated when they are available. In the interim, partial mitigations are available below. We do not recommend relying on containers as a security boundary, container breakout vulnerabilities are very common. Use GKE Sandbox instead. If possible, migrate your workloads to run as non-root. If your container needs to be root, consider setting the
|
Medium |
GDC (VMware)
Updated: 2026-05-20
| Description | Severity |
|---|---|
|
Container breakout vulnerabilities CVE-2026-43284 and CVE-2026-43500 have been found in the Linux kernel, known as DirtyFrag. They allow an unprivileged local attacker to escalate to root on the host. What should I do? |
Pending |
GKE on AWS
Updated: 2026-05-20
| Description | Severity |
|---|---|
|
Container breakout vulnerabilities CVE-2026-43284 and CVE-2026-43500 have been found in the Linux kernel, known as DirtyFrag. They allow an unprivileged local attacker to escalate to root on the host. What should I do? |
Pending |
GKE on Azure
Updated: 2026-05-20
| Description | Severity |
|---|---|
|
Container breakout vulnerabilities CVE-2026-43284 and CVE-2026-43500 have been found in the Linux kernel, known as DirtyFrag. They allow an unprivileged local attacker to escalate to root on the host. What should I do? |
Pending |
GDC (bare metal)
Updated: 2026-05-20
| Description | Severity |
|---|---|
|
Container breakout vulnerabilities CVE-22026-43284 and CVE-2026-43500 have been found in the Linux kernel, known as DirtyFrag. They allow an unprivileged local attacker to escalate to root on the host. What should I do?There is no action required. GDC software for bare metal isn't affected as it does not bundle an operating system in its distribution. |
None |