Servers and applications
GHSA-45qw-5wc8-pw8v
Cached ECR registry authorization token exposed to standard users in registry API responses
- 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
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
Portainer can integrate with Amazon Elastic Container Registry (ECR). For an ECR registry, Portainer caches a short-lived registry authorization token on the registry record and refreshes it when needed. The cached token is a working docker-login credential for the registry, valid for about 12 hours.
Two read endpoints that return registry records to standard users removed the stored password but not this cached token: the environment registry list (GET /api/endpoints/{id}/registries) and the registry inspection endpoint (GET /api/registries/{id}). Any authenticated standard user who could read a registry through either endpoint received the token and its expiry time in the response.
The issue is exploitable over the network with a single request. It needs a valid low-privilege account, no user interaction, and an ECR registry that holds a cached token.
Workarounds
Administrators who cannot immediately upgrade can reduce exposure by:
- Limit what the ECR credential can do. Use an AWS IAM principal for Portainer that has pull-only access to the specific repositories it needs, so a token obtained from Portainer carries only that scope. Least-privilege IAM is the deployer’s responsibility under Portainer’s shared responsibility security policy and limits what a token can do. Returning the token to standard users was Portainer’s responsibility, and is fixed.
- Reduce where the registry is assigned.
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-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
- GHSA-m2rf-p268-843wStack update lets users take over and overwrite stacks on environments they cannot accessHigh 7.1 19 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-45qw-5wc8-pw8v
- github.com https://github.com/portainer/portainer/security/advisories/GHSA-45qw-5wc8-pw8v