Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions
Security/Cloud Computing
Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions
Kubernetes Blog·Sep 16, 2026·9 min read
By By Nispriha Jagan (Red Hat), Neeraj Krishna Gopalakrishna (Red Hat) |
Wednesday, September 16, 2026
Vue.jsLinuxKubernetesSecurityAzureTerraformDocker
AI summary
Kubernetes v1.37 introduces new storage security features, including configurable mount options and directory permission modes for volumes. These enhancements address long-standing security risks by allowing users to apply Linux bind mount flags like noexec and nodev, alongside sticky bit directory permissions, directly via the Kubernetes API.
Key points
New bind mount options allow users to apply noexec, nosuid, and nodev flags to volumes for hardened security.
The EmptyDirVolumeMode feature allows setting custom permission bits, including the sticky bit, for emptyDir volumes.
These features mitigate the risk of arbitrary code execution in writable volume mounts, even when the container root filesystem is read-only.
Feature gates VolumeBindMountOptions and EmptyDirVolumeMode are available in alpha in Kubernetes v1.37.