Portainer: Bind-mount restriction bypass via HostConfig.Mounts

Summary

Portainer Community Edition is a lightweight service delivery platform for containerized applications that can be used to manage Docker, Swarm, Kubernetes and ACI environments. From 2.33.0 to before 2.33.8, 2.39.2, and 2.41.0, Portainer offers an environment-level Disable bind mounts for non-administrators security setting that blocks regular users from binding host paths into containers they create through the Portainer-mediated Docker API. The check that enforces this setting only inspected the legacy HostConfig.Binds array on the container-create proxy and never looked at the equivalent HostConfig.Mounts array. Any authenticated user with rights to create containers on a Docker environment where the restriction is enabled could submit a bind-typed entry under HostConfig.Mounts and mount any host path into their container. This vulnerability is fixed in 2.33.8, 2.39.2, and 2.41.0.

Timeline

1. May 28, 2026, 9:03 PM UTCCVE published
2. May 29, 2026, 7:08 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. May 29, 2026, 7:08 PM UTCRecord last updated

Affected versions

• portainer portainer

  From 2.33.0 · fixed in 2.33.8; From 2.39.0 · fixed in 2.39.2; From 2.40.0 · fixed in 2.41.0

• github.com/portainer/portainerGo

  From 2.33.0 · fixed in 2.33.8

• github.com/portainer/portainerGo

  From 2.39.0 · fixed in 2.39.2

• github.com/portainer/portainerGo

  From 2.40.0 · fixed in 2.41.0

• github.com/portainer/portainerGo

  All versions

References 1