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

Portainer CE 2.45.1

UPDATE_WITH_CARE

Security-related language in release notes; update after a backup if you are affected.

Published: 2026-09-17T02:11:43Z · 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 - Hardened outbound requests against SSRF. Helm chart resolution and Git HTTP/HTTPS operations now go through the SSRF-aware transport, and the static rules that enforce this now match by type rather than by import alias, so an aliased import can no longer slip past them - Certificate-based authentication for Azure Blob backups is now disabled in FIPS mode - Added build-time static analysis that catches FIPS violations before they ship - Removed unused non-FIPS code paths from FIPS builds …

Breaking changes

None detected by heuristics.

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.