Servers and applications
GHSA-9xr4-r82x-p44j
Compose `use_api_socket` bypasses the Hide bind mounts for non-administrators setting
- Severity
- High 8.7
- Published
- 19 Nov 2026
- Last changed
- 19 Nov 2026
- Added to UpHeron
- 19 Nov 2026
- Fixed in
- 2.39.9, 2.45.4, 3.1.0
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
Portainer lets non-administrator users deploy Docker Compose stacks to an environment, and when the per-environment setting Hide bind mounts for non-administrators is enabled, the stack validator IsValidStackFile rejects bind mounts declared in top-level volumes and each service's volumes. It never inspected a service's use_api_socket flag. When that flag is set, Docker Compose adds a bind mount of the Docker socket (/var/run/docker.sock) and a DOCKER_CONFIG carrying registry credentials to the service while bringing the stack up, after Portainer's validation has already passed. Any authenticated user with the Standard user role and stack-management access to a Docker standalone environment can exploit this.
Portainer operates a shared-responsibility security model: administrators decide how permissive each environment's security settings are, and Portainer is responsible for enforcing those settings as configured.
Workarounds
Administrators who cannot immediately upgrade can reduce exposure by:
- Hide the use of Stacks for non-administrators. In each Docker environment's settings, enable Hide the use of Stacks for non-administrators. Portainer then refuses stack creation and management from non-administrator users on the server side, which blocks this vector. It removes self-service stack deployment for those users; users with the environment administrator role can still deploy stacks.
- Limit standard-user environment access.
Affected software
| Software | Affected versions |
|---|---|
PortainerServers and applications · github:portainer/portainer |
|
About Portainer
Open source software to manage Docker, docker swarm and Kubernetes
- 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
Website Source code Docker image
Vulnerabilities in Portainer
- In our list
- 48
- Published in the last 12 months
- 30
- Critical, last 12 months
- 2
- High, last 12 months
- 15
- Known exploited
- 0
- GHSA-45qw-5wc8-pw8vCached ECR registry authorization token exposed to standard users in registry API responsesHigh 7.1 19 Nov 2026
- GHSA-2fmf-33r2-5vqgDocker network connect and disconnect let users attach or detach containers they cannot accessMedium 5.3 19 Nov 2026
- GHSA-6c57-xm2f-23fgWebSocket attach and exec let users open a shell in containers they cannot accessMedium 6.5 19 Nov 2026
- GHSA-xfw5-xx3q-mch6Stored Git credentials can be sent to an attacker-chosen host by users with read-only accessHigh 7.1 19 Nov 2026
- GHSA-83xv-v98x-cc83Stack list exposes Public stacks and their environment variables to users without access to the environmentMedium 6.0 19 Nov 2026
- GHSA-7pww-qg5m-5vpvGit stack redeploy exposes stored environment variables of stacks on environments the user cannot accessMedium 6.1 19 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-9xr4-r82x-p44j
- github.com https://github.com/portainer/portainer/security/advisories/GHSA-9xr4-r82x-p44j