Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    A bunch of old metal keys lying on a wooden table, shown in black and white.
    Image by weinstock from Pixabay

    Portainer 2.39.9 LTS fixes Critical Go flaws and access-control bypasses

    Automated source check Correction issued

    Portainer

    Update (2026-11-18): This advisory has changed: The Compose stack validator skipped services using profiles and did not check include; restrictions now apply to every service and include is rejected when bind mounts are disabled for regular users., according to github.com/portainer/portainer/releases/tag/2.39.9.

    Two Critical Go flaws fixed in 2.39.9 LTS

    Portainer 2.39.9 LTS delivers the security fixes and dependency updates listed in its release notes.

    The two flaws rated Critical are CVE-2026-56857 and CVE-2026-78663, both fixed by raising the Go toolchain from 1.25.14 to 1.26.10. CVE-2026-78663 is also covered by the golang.org/x/net update to 0.62.0. The notes give no CVSS scores, and most listed CVEs carry no severity at all.

    • grpc: CVE-2026-84304 and CVE-2026-84445, both rated High, are fixed by the update to 1.83.2.
    • containerd: CVE-2026-95837 (High) is fixed by the updates to 1.7.36 and 2.2.10.
    • Docker socket: non-administrators could reach the socket through the Compose use_api_socket option, and it is now blocked wherever regular users are denied bind mounts.
    • Docker networks: non-administrators could attach containers and stacks to networks they had no access to, and joins are now limited to accessible networks.
    • Console access: the /websocket/attach and /websocket/exec endpoints skipped container access control, and they now return 403 for containers a non-administrator cannot reach.
    • Stack start and stop: these could act on an environment other than the authorized one, so users could stop or overwrite same-named stacks elsewhere; they now return 403 except for administrators handling orphaned stacks.
    • Registry responses: they returned the stored ECR access token, and every registry response now clears it.

    The release notes list further lower-severity fixes beyond these. The kubectl shell image now uses Alpine 3.24.4, kubectl v1.37.1 and helm v4.3.1, and the notes say its CVE clearance is still to be confirmed with Docker Scout during the build. Check the commands and settings here against the documentation listed under Sources and your own setup before running them.

    Portainer 2.39.9 breaks eMudhra, curl and network setups

    • eMudhra certificates: Portainer no longer trusts them (CVE-2026-111943), following the compromise of eight eMudhra (emSign) intermediate CAs.
    • Connections that fail: OAuth/OIDC and LDAPS providers, registries and Git hosts presenting affected certificates stop working after the upgrade, and if your SSO or LDAP provider is affected, only the initial admin can sign in.
    • curl in the kubectl shell: the binary and its libraries are gone, so scripts calling it fail with curl not found; use wget, which busybox still provides, or point --kubectl-shell-image at an image that includes curl.
    • Shared networks: Compose or Swarm stacks from non-administrators that use a network they cannot access fail on start, update, Git redeploy and auto-update, so grant access to the network or have an administrator deploy the stack.

    Portainer 2.45.4 notes add Kubernetes permission changes

    The sources also include notes for 2.45.4, a later release than 2.39.9. Since 2.45.0, Kubernetes actions run under each user's own ServiceAccount, limited to the namespaces of their role. Non-administrator manifest deploys, Git and webhook redeploys, rolling restarts and Helm charts from Git can then fail with forbidden errors, including for stacks created before the upgrade. An administrator can deploy those resources, or the cluster can grant the extra permissions. Read-only and Helpdesk users can no longer see secret values, and a role such as Standard user or Operator in the namespace restores that.

    Podman support and kubectl image constraints

    Podman support is limited to CentOS 9 with rootful Podman 5, and the auto-onboarding script does not support Podman environments. The 2.45.4 notes say upgraded installs keep their existing kubectl shell image until you change it with --kubectl-shell-image, KUBECTL_SHELL_IMAGE or PUT /api/settings, while new installs get the new image. They also say in-app updates on Docker standalone and Swarm now pull the exact version tag instead of latest, so a private registry mirror must carry that tag or the update fails.

    Update to 2.39.9 after checking certificates and stacks

    Update to 2.39.9 LTS to get the fixes; the notes are on the Portainer GitHub releases page for that tag. Before you upgrade, look for non-administrator stacks that use shared networks, and check whether your SSO, LDAP, registries or Git hosts present eMudhra-issued certificates. No source says whether any of these flaws has been exploited in the wild.

    What the Portainer notes leave out

    The notes give no release date for 2.39.9 LTS and no disclosure date for the eMudhra CA compromise. The sources also give no download or availability details for 2.39.9 or 2.45.4.

    Product Affected Fixed
    Portainer Not stated in the release notes 2.39.9 LTS

    Sources

    Image: Image by weinstock from Pixabay


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion