Podman 3.2 · Version Status
Podman 3.2 End of Life Date
Podman 3.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Podman 3.2 is actively supported. EOL date: Supported indefinitely.
EOL Date
Supported indefinitely
Supported
Latest Release
3.2.3
Standard release
Release Date
Jun 3, 2021
Podman 3.2 series
| Version | Latest | EOL Date | Status |
|---|
| 3.0 |
3.0.2 |
Supported |
Active |
| 3.1 |
3.1.2 |
Supported |
Active |
| → 3.2 |
3.2.3 |
Supported |
Active |
| 3.3 |
3.3.1 |
Supported |
Active |
| 3.4 |
3.4.7 |
Supported |
Active |
| 4.0 |
4.0.3 |
Supported |
Active |
| 4.1 |
4.1.1 |
Supported |
Active |
| 4.2 |
4.2.1 |
Supported |
Active |
What does Podman 3.2 end of life mean?
When Podman 3.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Podman 3.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Podman 5.8 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Podman 3.2 reach end of life?
Podman 3.2 has no scheduled end-of-life date and is supported indefinitely.
Is Podman 3.2 still supported?
Yes, Podman 3.2 is currently supported. The EOL date is Supported indefinitely.
What should I upgrade to from Podman 3.2?
The recommended upgrade from Podman 3.2 is
Podman 5.8 — the latest actively supported version. Check the
Podman full timeline for all supported versions.
What are the security risks of running Podman 3.2 past EOL?
When Podman 3.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Podman should migrate immediately or implement compensating controls.