All vulnerabilities

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.

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

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.
Workarounds as given by portainer/portainer's security advisory.

Affected software

SoftwareAffected versions
PortainerServers and applications · github:portainer/portainer
  • From 2.39.0 before 2.39.9
  • From 2.40.0 before 2.45.4
  • From 3.0.0 before 3.1.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