You need to enable JavaScript to run this app.
Volcengine Kubernetes Engine

Volcengine Kubernetes Engine

Copy page
Download PDF
Security announcements
containerd vulnerability fixed (CVE-2026-53488)
Copy page
Download PDF
containerd vulnerability fixed (CVE-2026-53488)
Background information​
containerd is an industry‑standard container runtime widely used in the cloud‑native ecosystem. It often functions as the CRI container runtime add-on for Kubernetes nodes.​
CVE-2026-53488 is a label trust boundary flaw in the containerd CRI add-on. The CRI propagates Dockerfile LABEL from the image configuration to Container labels. This allows attackers to inject reserved namespace labels such as containerd.io/ or io.cri-containerd via malicious images. Through the log URI mechanism containerd.io/restart.loguri=binary://... of the restart monitor, an attacker can launch any log binary programs in the host context to run commands with host root privileges. For more information, see Volcano Engine security announcement.​
Vulnerability severity​
Critical​
Scope of impact​
The following containerd versions are affected by this vulnerability:​
  • containerd < v1.6.38-vke.18​
  • containerd < v2.1.9-vke.1​
Remediation​
VKE has released the following patched versions. Promptly upgrade the version to the latest patched version. For detailed steps, see Upgrading clusters.​
  • containerd >= v1.6.38-vke.18​
  • containerd >= v2.1.9-vke.1​
Before the upgrade, read and assess the change impact to prevent potential traffic disruption. For a list of containerd versions released by VKE, see Containerd runtime release notes.​
  • Newly created VKE clusters and node pools are not affected by this vulnerability.​
  • For VKE node pools within the affected scope, upgrade the node runtime configuration to the latest patched version. This operation takes effect on newly added nodes. For upgrade steps, see Managing node pools.​
  • For VKE clusters or nodes within the affected scope, upgrade the clusters to the latest patched version. This operation takes effect on existing nodes. For detailed steps, see Upgrading clusters.​
  • If you cannot use the cluster upgrade feature, submit a ticket to obtain technical support.​
Last updated: 2026.07.10 18:23:35