Podman End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Podman versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.0 | 3.0.2 | Feb 11, 2021 | No EOL date | Supported | Active |
| 3.1 | 3.1.2 | Mar 29, 2021 | No EOL date | Supported | Active |
| 3.2 | 3.2.3 | Jun 3, 2021 | No EOL date | Supported | Active |
| 3.3 | 3.3.1 | Aug 20, 2021 | No EOL date | Supported | Active |
| 3.4 | 3.4.7 | Sep 30, 2021 | No EOL date | Supported | Active |
| 4.0 | 4.0.3 | Feb 17, 2022 | No EOL date | Supported | Active |
| 4.1 | 4.1.1 | May 5, 2022 | No EOL date | Supported | Active |
| 4.2 | 4.2.1 | Aug 10, 2022 | No EOL date | Supported | Active |
| 4.3 | 4.3.1 | Oct 18, 2022 | No EOL date | Supported | Active |
| 4.4 | 4.4.4 | Feb 1, 2023 | No EOL date | Supported | Active |
| 4.5 | 4.5.1 | Apr 14, 2023 | No EOL date | Supported | Active |
| 4.6 | 4.6.2 | Jul 20, 2023 | No EOL date | Supported | Active |
| 4.7 | 4.7.2 | Sep 27, 2023 | No EOL date | Supported | Active |
| 4.8 | 4.8.3 | Nov 27, 2023 | No EOL date | Supported | Active |
| 4.9 | 4.9.5 | Jan 22, 2024 | No EOL date | Supported | Active |
| 5.0 | 5.0.3 | Mar 19, 2024 | May 29, 2024 | 755 days past EOL | EOL |
| 5.1 | 5.1.2 | May 29, 2024 | Aug 1, 2024 | 691 days past EOL | EOL |
| 5.2 | 5.2.5 | Aug 1, 2024 | Nov 12, 2024 | 588 days past EOL | EOL |
| 5.3 | 5.3.2 | Nov 12, 2024 | Feb 11, 2025 | 497 days past EOL | EOL |
| 5.4 | 5.4.2 | Feb 11, 2025 | May 13, 2025 | 406 days past EOL | EOL |
| 5.5 | 5.5.2 | May 13, 2025 | Aug 15, 2025 | 312 days past EOL | EOL |
| 5.6 | 5.6.2 | Aug 15, 2025 | Nov 11, 2025 | 224 days past EOL | EOL |
| 5.7 | 5.7.1 | Nov 11, 2025 | Feb 12, 2026 | 131 days past EOL | EOL |
| 5.8 | 5.8.3 | Feb 12, 2026 | TBD | Supported | Active |
What does Podman end of life mean for your organization?
When a version of Podman reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Podman should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Podman versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →