Servers and applications
GHSA-m2rf-p268-843w
Stack update lets users take over and overwrite stacks on environments they cannot access
- Severity
- High 7.1
- 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
- Change data · Slow it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
Portainer lets users with stack-management rights update an existing stack through the stack update API, which takes the stack's numeric ID and an endpointId environment parameter. The handler loaded the stack by ID and then overwrote the stack's persisted environment with the request-supplied value before running any authorization. The environment access check and the stack ownership (ResourceControl) check therefore evaluated against the caller's environment rather than the environment the stack actually belongs to. Any authenticated standard user with stack-management rights on one environment could target a stack on an environment they cannot access.
For Compose and Swarm stacks the attacker also creates a stack with the same name on their own environment, which supplies a matching ownership record that satisfies the second check. For Kubernetes stacks no such stack is needed.
Workarounds
Administrators who cannot immediately upgrade can reduce exposure by:
- Limit who can manage stacks. Remove stack-management permissions from standard users on environments where they are not needed. The attack requires stack-management rights on at least one environment.
- Audit stack ownership. Look for stacks whose recorded environment differs from the environment they were created on, or whose last updater is not the user or team that owns them.
- Review access to environments. Confirm that standard users and teams only have access to the environments they require.
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-m2rf-p268-843w
- github.com https://github.com/portainer/portainer/security/advisories/GHSA-m2rf-p268-843w