All vulnerabilities

Servers and applications

CVE-2026-44850

Bind-mount restriction bypass via HostConfig.Mounts

Severity
High 8.5
Published
10 May 2026
Last changed
21 Jul 2026
Added to UpHeron
1 Nov 2026
Fixed in
2.33.8, 2.39.1, 2.39.2, 2.41.0
Exploit chance
0.2% in the next 30 daysHigher than 14% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Incorrect authorization (CWE-863)
Attack
Over the network · Needs a user account · No user action needed
Attacker can
Read data · Change some data
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Also known as
GHSA-7fw3-x4r2-g7wc
Sources
NVD, Project advisories (GitHub)

Description

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.

The two fields are interchangeable on the Docker daemon — both produce real bind mounts at runtime — so a check that inspects only one is functionally equivalent to no check at all. The same primitive is correctly enforced on Swarm service create against TaskTemplate.ContainerSpec.Mounts; the gap was specific to the POST /containers/create proxy path.

From portainer/portainer's security advisory. Shortened; the full text is there.

Workarounds

Administrators who cannot immediately upgrade can reduce exposure by:

  • Revoke container-create rights from non-administrator accounts on affected environments. If the bind-mount restriction is being relied on as a hard guarantee, audit which non-administrator accounts have container-create rights on environments where it is set, and downgrade those accounts to roles that lack container-create until the patched release is deployed. Stack and service deployment that depends on container-create will stop working for those users until the patched release is in place.
Workarounds as given by portainer/portainer's security advisory.

Affected software

SoftwareAffected versions
PortainerServers and applications · cpe:a:portainer:portainer
  • From 2.33.0 before 2.33.8
  • From 2.34.0 before 2.39.1
  • Version 2.40.0
PortainerServers and applications · github:portainer/portainer
  • From 2.33.0 before 2.33.8
  • From 2.39.0 before 2.39.2
  • From 2.40.0 before 2.41.0

About Portainer

Open source software to manage Docker, docker swarm and Kubernetes

From Wikidata, CC0 1.0.
Docker Hub pulls
1,590,442,292Docker Hub, 15 Nov 2026
GitHub stars
38,831GitHub, 15 Nov 2026
Forks
2,940GitHub, 15 Nov 2026
Latest release
2.45.3GitHub, 15 Nov 2026
Released
21 Oct 2026GitHub
License
ZlibGitHub
First published on GitHub
19 May 2016GitHub

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-44850
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-44850
  • GitHub Advisory Database https://github.com/advisories/GHSA-7fw3-x4r2-g7wc
  • github.com https://github.com/portainer/portainer/security/advisories/GHSA-7fw3-x4r2-g7wc