Servers and applications
GHSA-34v4-j95q-vx5r
Docker network resource control is not enforced when non-administrators attach containers, services, builds or stacks to a network
- 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
- Weakness
- Authorization bypass through a user-controlled key (IDOR) (CWE-639)Missing authorization (CWE-862)
- 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:N- Sources
- Project advisories (GitHub)
Description
Portainer applies resource control to Docker networks so that a Standard User can only use networks they own or were granted access to. This control was enforced when connecting or disconnecting a container to a network, but not when a container, service, image build or stack was created already attached to a named network. A Standard User could therefore place a workload they control on another user's or team's private network.
The container creation, Swarm service create and update, and image build handlers inspect other request fields but did not authorize the networks named in the request, and stack deployments did not check external or renamed networks. Any authenticated Standard User with permission to create containers, services, builds or stacks on a Docker environment could use this, provided they could learn the target network's name or ID.
Workarounds
- Limit who can create workloads on shared Docker environments. The issue requires a Standard User with permission to create containers, services, builds or stacks. Restricting that access to trusted users removes the exposure, at the cost of those users' self-service.
- Do not rely on network membership as the only protection for sensitive services. Require authentication and encryption on services shared over Docker networks, so that reaching the network is not enough.
- Audit for unexpected attachments.
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-34v4-j95q-vx5r
- github.com https://github.com/portainer/portainer/security/advisories/GHSA-34v4-j95q-vx5r