Stack Watch
Self-hosted update briefs — is it safe to update, or wait?
Disclaimer: Automated heuristics over public release notes and vulnerability databases (OSV / NVD). Can be wrong or incomplete. Always back up first and validate upgrades yourself. Stack Watch does not invent CVE IDs or issue counts. This is an MVP research project, not a live paid service.
Home / Portainer CE / 2.45.3

Portainer CE 2.45.3

BREAKING

Breaking-change language found in notes (1 hit(s)). Read migration steps before updating.

Published: 2026-10-22T07:15:49Z · GitHub release

Summary of changes

## Known issues - On Async Edge environments, an invalid update schedule date can be displayed when browsing a snapshot ## Known issues with Podman support - Podman environments aren't supported by auto-onboarding script - It's not possible to add Podman environments via socket, when running a Portainer server on Docker (and vice versa) - Support for only CentOS 9, Podman 5 rootful ## Changes ## Breaking changes - Portainer no longer trusts TLS certificates issued by eMudhra (emSign), following the compromise of eight eMudhra intermediate CAs (CVE-2026-111943). Connections to services that present an affected certificate, including OAuth/OIDC and LDAPS providers, registries and Git hosts, will fail after the upgrade. If your single sign-on or LDAP provider is affected, only the initial admin will be able to sign in. Check your services before upgrading. See this FAQ for details. …

Breaking changes

CVEs linked to this release

None linked from release notes or OSV fixed-in match.

Linked issues / PRs mentioned

not stated in release notes

Back up first

Always back up first. Stack Watch briefs are automated heuristics over public release notes and vulnerability databases. They can be wrong or incomplete. You are responsible for validating upgrades in your own environment. We never invent CVE IDs or issue counts — if a number is missing, it was not found.