CVE Watchtower

CVE-2026-44882Portainer Portainer Incorrect Authorization

NVDCVSS scored by security-advisories@github.com

Vulnerability Summary

Portainer Community Edition is a lightweight service delivery platform for containerized applications that can be used to manage Docker, Swarm, Kubernetes and ACI environments. From 2.33.0 to before 2.33., Portainer proxies requests to Kubernetes clusters through a middleware layer (kubeClientMiddleware) that validates the requesting user's token before forwarding traffic to the cluster. When security.RetrieveTokenData returned an error, the middleware wrote an HTTP 403 response but was missing a return statement β€” execution continued into the handler with a nil tokenData value. The Kubernetes endpoints sit behind Portainer's outer AuthenticatedAccess bouncer, so an attacker requires a valid Portainer session. However, a user whose secondary token validation fails in kubeClientMiddleware β€” for example a user without permission to access a given Kubernetes endpoint β€” would have their request forwarded to the cluster anyway, bypassing the authorization check. The same defect was present in both the CE and EE codebases. This vulnerability is fixed in 2.33.8.
Severity Level
HIGH(8.1)
Published Date
May 28, 2026
Last Modified
Jul 21, 2026
Exploitation Status
Public exploit available
EPSS Score (30-Day)
0.34%Probability
Root Weakness (CWE)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
CVSS v3.1 Base Metrics — Score 8.1 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • Portainer Portainer >= 2.33.0 and < 2.33.8
  • portainer >= 2.33.0, < 2.33.8
Patched Versions
  • Portainer Portainer 2.33.8

What to do

Prioritize this fix. Exploit code is public, so attacks can follow quickly.

  1. Check whether you run Portainer Portainer and which version.
  2. Update to a patched version listed above, then confirm the new version.
  3. Review logs and exposed services for signs of earlier compromise.

Timeline

  • May 28, 2026Published
  • Jul 21, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Portainer Portainer CVEsYou are reading CVE-2026-44882. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 22, 2026 22:07 UTC