HighGHSA-mvff-h3cj-wj9cCVE-2021-43816GO-2022-0278

Unprivileged pod using `hostPath` can side-step active LSM when it is SELinux

Published 6 Jan 2022 · Updated 8 Jul 2026

Is your project on an affected github.com/containerd/containerd?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=1.5.0 <1.5.9
Fixed in
1.5.9
Update to the fixed version for your release line, for example:go get github.com/containerd/containerd@v1.5.9

Details

Impact

Containers launched through containerd’s CRI implementation on Linux systems which use the SELinux security module and containerd versions since v1.5.0 can cause arbitrary files and directories on the host to be relabeled to match the container process label through the use of specially-configured bind mounts in a hostPath volume. This relabeling elevates permissions for the container, granting full read/write access over the affected files and directories. Kubernetes and crictl can both be configured to use containerd’s CRI implementation.

If you are not using containerd’s CRI implementation (through one of the mechanisms described above), you are not affected by this issue.

Patches

This bug has been fixed in containerd 1.5.9. Because file labels persist independently of containerd, users should both update to these versions as soon as they are released and validate that all files on their host are correctly labeled.

Workarounds

Ensure that no sensitive files or directories are used as a hostPath volume source location. Policy enforcement mechanisms such a Kubernetes Pod Security Policy AllowedHostPaths may be specified to limit the files and directories that can be bind-mounted to containers.

For more information

If you have any questions or comments about this advisory:

  • Open an issue in containerd
  • Email us at [security@containerd.io](mailto:security@containerd.io)

Is GHSA-mvff-h3cj-wj9c in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/containerd/containerd, and gives you the command that fixes it.

More advisories for github.com/containerd/containerd

  • LowCVE-2026-95837containerd CRI plugin: Checkpoint restore bypasses destination security context in github.com/containerd/containerd · 19 Oct 2026
  • LowCVE-2026-95838containerd: Unpack DoS via repeated opaque whiteouts in github.com/containerd/containerd · 19 Oct 2026
  • MediumCVE-2026-95838containerd: Unpack DoS via repeated opaque whiteouts · 15 Oct 2026
  • LowCVE-2026-53493Containerd has image-pull DoS via crafted OCI index graph amplification in github.com/containerd/containerd · 1 Oct 2026
  • MediumCVE-2026-53493Containerd has image-pull DoS via crafted OCI index graph amplification · 25 Sept 2026
  • LowCVE-2026-53495containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service in github.com/containerd/containerd · 16 Sept 2026
All 48 advisories for github.com/containerd/containerd

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.