In this article
Portainer lets Standard Users join other teams' networks
Portainer's network resource control is skipped when a workload is created already attached to a named network. A Standard User who can create containers, services, builds or stacks can place that workload on another user's or team's private Docker network, if they know the network's name or ID.
Portainer rates the advisory Medium severity. On Portainer itself, the effect is a skipped resource-control decision with low confidentiality and integrity impact.
A workload on the network can reach services exposed only there, resolve other workloads by name and observe traffic that shares the network. The advisory says this alone does not give administrator access or access to the Docker host. What an intruder can actually reach depends on authentication and encryption of services on the other tenant's network, which Portainer does not control.
Create requests skip the check Portainer runs on connect
Resource control means a Standard User can only use Docker networks they own or were granted. Portainer enforced that when connecting or disconnecting a container, but not when a workload was created on a named network.
The container create, Swarm service create and update, and image build handlers do not authorize the networks named in the request. Stack deployments do not check external or renamed networks. A follow-up fix also covers the network identifier in a container's endpoint configuration and in network connect requests.
Portainer 2.39.x to 2.45.x and 3.0.x are affected
Every release of the 2.39.x LTS line from 2.39.0, the 2.45.x LTS line from 2.45.0, and the 3.0.x line from 3.0.0 is vulnerable. Portainer 2.40.x to 2.44.x (STS) are also affected.
Releases before 2.39.0 are end-of-life and will not get a fix. The advisory covers Community Edition and Business Edition, except that 3.x is not part of the Community Edition line. The advisory gives no CVSS score and does not say whether the flaw has been exploited, so the exploitation status is unknown.
Update to Portainer 2.45.4, 2.39.9 or 3.1.0
The fixes are 2.39.9 for the 2.39.x LTS line, 2.45.4 for the 2.45.x LTS line and 3.1.0 for the 3.x line. Community Edition has no 2.39.9 build, so Community Edition users should upgrade to 2.45.4. Portainer 3.0.x gets no dedicated patch and reaches end of life on 2026-11-19, so move 3.0.x installs to 3.1.0.
If you cannot update yet, the advisory lists these stopgaps:
- Limit who can create containers, services, builds or stacks on shared Docker environments to trusted users.
- Require authentication and encryption on services shared over Docker networks, so reaching a network is not enough to use them.
- For each non-administrator workload, check its attached networks against the networks that user can access in Portainer, and investigate any difference.
The advisory states that none of these workarounds replace the fix.
What the Portainer advisory does not give
No CVE identifier is given; the advisory is identified only by its GHSA id. It also gives no disclosure or patch release date.
| Product | Affected | Fixed |
|---|---|---|
| Portainer 2.39.x LTS | 2.39.0 and later releases in the 2.39.x line | 2.39.9 |
| Portainer 2.45.x LTS | 2.45.0 and later releases in the 2.45.x line | 2.45.4 |
| Portainer 3.x | 3.0.x from 3.0.0 | 3.1.0 |
Sources
- github.com/portainer/portainer/security/advisories/GHSA-34v4-j95q-vx5r
- github.com/portainer/portainer/security/advisories/GHSA-26fg-hrxq-h6v4
Image: “Lock and Key | 1700–1730” by museado, CC0 1.0, via flickr (Openverse)
This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].




Discussion