|
What is the Vulnerability? |
High-severity vulnerabilities in runc (CVE-2025-31133, CVE-2025-52565, CVE-2025-52881) were disclosed in early November 2025. A malicious or compromised container image can abuse how runc handles masked paths, bind-mounts, and special files to write to the host /proc filesystem and escape the container boundary – enabling remote code execution on the host, persistence, or cluster-wide denial-of-service. These issues affect virtually all Linux container stacks that use runc (Docker, containerd, CRI-O, Kubernetes, and managed services) CVE-2025-31133 – Incorrect handling of masked paths; attacker can replace container /dev/null with a symlink and possibly escape. |
|
What is the recommended Mitigation? |
Patch runc/update node images: Apply vendor runc updates. AWS lists patched runc (package version runc-1.3.2-2 for Amazon Linux variants) and updated AMIs/Bottlerocket releases; AWS also automated Fargate/ECS updates where applicable. If using other distros, install the distribution-provided patched runc packages per vendor guidance. Audit & logging: Enable container runtime logs, containerd/dockerd debug for suspicious mount/bind events. |
|
What FortiGuard Coverage is available? |
|