Servers and applications
GHSA-hjgg-rj83-gwfx
Swarm service force-update lets users restart services 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
- Weakness
- Missing authorization (CWE-862)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Change some data · Slow it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
Portainer lets administrators restrict Docker resources, including Swarm services, to particular users and teams through resource controls. A non-administrator who has access to an environment can normally act only on the services a resource control makes accessible to them, and the Docker API proxy enforces this on every service request.
Portainer also exposes a dedicated endpoint, PUT /api/endpoints/{id}/forceupdateservice, that force-updates a Swarm service and optionally re-pulls its image. This endpoint checked only that the caller had access to the environment. It never checked the resource control of the service named in the request, so any authenticated user with access to a Swarm environment could force-update a service they are denied access to.
Portainer operates a shared-responsibility security model: administrators decide who may access each environment and each resource, and Portainer is responsible for enforcing those decisions as configured.
Workarounds
Administrators who cannot immediately upgrade can reduce exposure by:
- Limit Standard-user access to Swarm environments. Remove environment access from users and teams who do not need it. The attack needs access to the environment that runs the service.
- Use a role without service update rights (Business Edition). The Helpdesk and Read-only User roles cannot call this endpoint.
Docker standalone environments are not affected, as the endpoint acts only on Swarm services. None of these replace the fix.
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-hjgg-rj83-gwfx
- github.com https://github.com/portainer/portainer/security/advisories/GHSA-hjgg-rj83-gwfx