The Portainer container isolation flaw lets an authenticated Standard user with access to a shared environment open an interactive session in another team’s container. Portainer published fixes on November 19, 2026: 2.39.9, 2.45.4, and 3.1.0. Administrators should identify shared environments and match each installed release to its branch before updating.
The Portainer security advisory covers both Community Edition and Business Edition. Affected remote and Edge-managed environments also use the vulnerable WebSocket authorization path. Put those environments in the same patch inventory as directly managed ones. Compare the advisory and fixed versions with your installed control-plane inventory as part of a vulnerability intelligence platform workflow.
Which Versions Fix the Portainer Container Isolation Flaw?
Portainer lists three affected release ranges and a fixed release for each. The table applies to both editions, but Community Edition receives updates only on the 2.45 line. Confirm the edition and running version on every control plane before closing a change.
| Installed release range | Fixed release | Operator decision |
|---|---|---|
| 2.39.0 through 2.39.8 | 2.39.9 | Portainer recommends moving 2.39.x users to 2.45.4 or later. |
| 2.40.0 through 2.45.3 | 2.45.4 | Update to 2.45.4 or a later supported release. |
| 3.0.0 through 3.0.x | 3.1.0 | Move off the end-of-life 3.0 line to 3.1.0. |
Portainer says releases earlier than 2.39.0 are end of life and will receive no fix. Treat them as migration work, not as evidence of safety. Record each target version in the patch management record.
Why Does a Standard User Have Cross-Tenant Access?
The attach and exec WebSocket handlers checked permission for the environment but skipped the container ownership control. A Standard user with environment access could reach a container that Portainer’s resource controls assigned to another user or team. The advisory says the same gap reaches agent and Edge WebSocket proxies.
Portainer describes an interactive root session inside the target container, where the user could read or change workload data and disrupt processes. Host-wide control depends on deployment choices, such as a privileged container or a mounted Docker socket. The flaw does not by itself mean every affected host has been compromised.
The CVE Program published CVE-2026-134804 on November 22. Its record rates the issue 8.7 under CVSS 4.0 and 8.8 under CVSS 3.1, both High. Portainer’s advisory still displays 6.5 under CVSS 4.0, so use the documented access boundary and deployment impact to set priority.
What Should Portainer Administrators Do Now?
Prioritize environments where users or teams share access but should not reach each other’s containers. Portainer’s temporary guidance is to grant environment access only to people trusted with every container there.
- Inventory shared environmentsRecord each Portainer edition, running version, environment, and access owner.
- Apply the branch fixUpdate to a supported fixed release and verify the running version afterward.
- Reduce interim exposureSeparate mutually untrusted tenants into distinct environments until the fix is installed.
- Review session activityExamine attach and exec access records for sessions outside a caller’s container ownership.
Portainer also advises reviewing requests that used abbreviated container identifiers. Its workarounds reduce exposure but do not replace the fix. If the review identifies unauthorized access, use an incident response plan template to assign evidence preservation and recovery owners.
Keep the patch decision tied to the affected environment, not only the central Portainer instance. The vulnerability management workflow can track version verification and exceptions across teams. Revisit each exception until every shared environment runs a fixed release or has been retired.
Frequently Asked Questions
Which Portainer versions contain the fix?
Portainer lists 2.39.9, 2.45.4, and 3.1.0 as fixed releases for the affected 2.39, 2.40 through 2.45, and 3.0 ranges.
Can a Standard user reach another tenant’s container?
Portainer says a Standard user with access to a shared environment could open a session in a container owned by another user or team.
What should administrators do before patching is complete?
Portainer advises limiting environment access to users trusted with every container there and separating mutually untrusted tenants into distinct environments.
