Servers and applications
GHSA-2fmf-33r2-5vqg
Docker network connect and disconnect let users attach or detach containers they cannot access
- Severity
- Medium 5.3
- 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 some data · Change some data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:L- Sources
- Project advisories (GitHub)
Description
Portainer proxies Docker API requests and enforces per-object resource control on them. The Docker network connect and disconnect operations (POST /networks/{id}/connect and POST /networks/{id}/disconnect) act on two objects: the network named in the URL and the container named in the Container field of the JSON body. Portainer authorized only the network, and never put the container through a container resource-control check.
A closely related defect affected the same routes. Docker accepts network names that contain a /. Portainer's route matching did not recognise such a network id, so the request fell through to a default handler that authorized only the last path segment of the URL, a value the caller could choose, while the Docker daemon acted on the real network. This skipped the network checks for connect, disconnect, inspect and delete, and also skipped the container check described above.
Workarounds
Administrators who cannot immediately upgrade can reduce exposure by:
- Limit Standard user access to Docker environments. The issue requires an authenticated non-administrator with access to the environment. Remove access for users who do not need it.
- Audit network membership. Review which containers are attached to which user-created networks, and look for unexpected connect or disconnect activity in the Docker daemon events and the Portainer activity log.
- Treat networks as shared among users of an environment until patched.
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-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
- GHSA-m2rf-p268-843wStack update lets users take over and overwrite stacks on environments they cannot accessHigh 7.1 19 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-2fmf-33r2-5vqg
- github.com https://github.com/portainer/portainer/security/advisories/GHSA-2fmf-33r2-5vqg