Complete end-of-life dates, support windows, and security status for all Postmarketos versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 21.06 | 21.06 | Jul 4, 2021 | Jan 29, 2022 | 1561 days past EOL | EOL |
| 21.12 | 21.12 | Dec 29, 2021 | Jul 12, 2022 | 1397 days past EOL | EOL |
| 22.06 | 22.06 | Jun 12, 2022 | Jan 18, 2023 | 1207 days past EOL | EOL |
| 22.12 | 22.12 | Dec 18, 2022 | Jul 7, 2023 | 1037 days past EOL | EOL |
| 23.06 | 23.06 | Jun 7, 2023 | Jan 18, 2024 | 842 days past EOL | EOL |
| 23.12 | 23.12 | Dec 18, 2023 | Jul 16, 2024 | 662 days past EOL | EOL |
| 24.06 | 24.06 | Jun 16, 2024 | Jan 23, 2025 | 471 days past EOL | EOL |
| 24.12 | 24.12 | Dec 23, 2024 | Jul 23, 2025 | 290 days past EOL | EOL |
| 25.06 | 25.06 | Jun 23, 2025 | Jan 23, 2026 | 106 days past EOL | EOL |
| 25.12 | 25.12 | Dec 23, 2025 | Already EOL | Supported | Active |
When a Postmarketos version 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 Postmarketos 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →