By vendor

Portainer vulnerabilities

Known CVEs affecting Portainer products, prioritized by severity, with SEC.co remediation and detection guidance.

7 published vulnerabilities

• CVE-2026-44848HIGH 8.8

  Portainer Community Edition versions 2.33.0 through 2.33.7, 2.39.x (before 2.39.2), and 2.40.x (before 2.41.0) fail to properly restrict access to Docker plugin management endpoints. This means any standard user granted access to a Docker endpoint through Portainer can perform privileged operations like installing and enabling plugins directly on the underlying Docker daemon—something normally restricted to administrators. The flaw stems from missing access control handlers on the /plugins/* endpoints, allowing RBAC bypass for a critical management function.

• CVE-2026-44849HIGH 8.8

  Portainer Community Edition has a security control bypass where administrators can restrict what kinds of containers non-admin users are allowed to launch—such as preventing privileged containers or restricting device access. However, when users create containers through the Docker Swarm API instead of the standard container creation path, several of these restrictions are ignored. An authenticated attacker with basic user privileges could bypass these restrictions to launch more dangerous containers than policy allows. The issue affects versions 2.33.0 through 2.33.7, 2.39.0 through 2.39.1, and 2.40.x, with fixes available in 2.33.8, 2.39.2, and 2.41.0.

• CVE-2026-44850HIGH 8.5

  Portainer Community Edition versions 2.33.0 through 2.33.7, 2.39.0–2.39.1, and 2.40.x contain a security bypass in their bind-mount restriction feature. Organizations using Portainer to enforce a policy that prevents regular users from mounting host directories into containers can be circumvented. An authenticated user with container-creation rights can work around the restriction by using an alternative API field (HostConfig.Mounts) that the security check failed to inspect, allowing them to mount sensitive host paths into containers they control. This bypasses intended access controls and exposes host data to authenticated container users.

• CVE-2026-44882HIGH 8.1

  Portainer Community Edition versions 2.33.0 through 2.33.7 contain an authorization bypass vulnerability in how it proxies requests to Kubernetes clusters. When a user's token validation fails during a security check, the application incorrectly continues processing the request instead of stopping it. This allows an authenticated Portainer user without permission to access a specific Kubernetes cluster to send requests directly to that cluster anyway, circumventing the intended access controls. An attacker must already have a valid Portainer session to exploit this.

• CVE-2026-44883HIGH 7.5

  Portainer Community Edition versions between 2.33.0 and 2.33.7, 2.39.1, and 2.40.x contain a flaw in how they handle authentication tokens. The platform accepts JWT authentication tokens passed as URL query parameters (e.g., ?token=<JWT>) alongside the standard Authorization header. Because URLs are logged in reverse-proxy access logs, browser history, and Referer headers, tokens transmitted this way can be intercepted by anyone with access to those logs or by downstream websites users visit. Any leaked token provides complete access to the user's account for up to 8 hours (or longer if expiration is customized). This particularly affects users with container exec or attach permissions, not just administrators.

• CVE-2026-44884MEDIUM 6.5

  Portainer Community Edition versions 2.33.0 through 2.33.7 and 2.39.0 contain a flaw that lets any logged-in user view template files they shouldn't have access to. By trying different ID numbers, an attacker can enumerate and read custom template files that may hold sensitive credentials or connection strings—data that administrators likely assume only authorized users can see. The vulnerability has been patched in versions 2.33.8 and 2.39.1.

• CVE-2026-44885MEDIUM 5.5

  Portainer Community Edition versions 2.33.0 through 2.33.7 contain a directory traversal flaw in the backup restore function. When administrators upload a .tar.gz backup file to restore Portainer's configuration, the extraction process fails to properly validate file paths. A malicious backup archive can exploit this to write files outside the intended directory, potentially placing them anywhere on the server filesystem—for instance, in cron job directories or other sensitive locations. An attacker with high-level privileges (such as admin access) can craft a backup to inject malicious files into the host system during restoration. The vulnerability is resolved in version 2.33.8.