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.0

Portainer CE 2.45.0

UPDATE_WITH_CARE

Security-related fix signals present (linked: CVE-2026-44849). Prefer updating soon after a backup.

Published: 2026-08-27T06:41:31Z · 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 ## New and improved features - Added advanced Kubernetes node drain options with agent failover - Added native Portainer APIs for writing Kubernetes secrets, configmaps, deployments and persistent volume claims, replacing direct kube-apiserver proxy calls - Added a generic Kubernetes manifest dry-run API - Edge Compute settings can now be configured during initial setup and via cli flags …

Breaking changes

None detected by heuristics.

CVEs linked to this release

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.