postmarketOS End of Life (EOL) Dates & Support Timeline
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.
postmarketOS 26.06 is supported until January 31, 2027, its end-of-support date. It is also the next postmarketOS version to reach end of life. 12 of 13 tracked postmarketOS versions are past end of life; the most recent to reach it, 25.12, did so on July 31, 2026. The full postmarketOS lifecycle, with every version's release and end-of-support date, is in the table below.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 20.05 | — | May 31, 2020 | Apr 30, 2021 | 1972 days past EOL | EOL |
| 21.03 | — | Mar 31, 2021 | Aug 4, 2021 | 1876 days past EOL | EOL |
| 21.06 | — | Jul 4, 2021 | Jan 29, 2022 | 1698 days past EOL | EOL |
| 21.12 | — | Dec 29, 2021 | Jul 12, 2022 | 1534 days past EOL | EOL |
| 22.06 | 22.06 | Jun 12, 2022 | Jan 18, 2023 | 1344 days past EOL | EOL |
| 22.12 | 22.12 | Dec 18, 2022 | Jul 7, 2023 | 1174 days past EOL | EOL |
| 23.06 | 23.06 | Jun 7, 2023 | Jan 18, 2024 | 979 days past EOL | EOL |
| 23.12 | 23.12 | Dec 18, 2023 | Jul 16, 2024 | 799 days past EOL | EOL |
| 24.06 | 24.06 | Jun 16, 2024 | Jan 23, 2025 | 608 days past EOL | EOL |
| 24.12 | 24.12 | Dec 23, 2024 | Jul 23, 2025 | 427 days past EOL | EOL |
| 25.06 | 25.06 | Jun 22, 2025 | Jan 23, 2026 | 243 days past EOL | EOL |
| 25.12 | 25.12 | Dec 23, 2025 | Jul 31, 2026 | 54 days past EOL | EOL |
| 26.06 | — | Jun 21, 2026 | Jan 31, 2027 | 130 days remaining | Warning |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/postmarketos)
postmarketOS release and support pattern
Across the 13 release lines with a published release date, postmarketOS has shipped a new line roughly every 6 months (median interval). A line typically stays supported for about 7 months from its release to its end-of-life date.
Of the 13 release lines tracked, 12 are past end of life and 1 is still within support. The newest line, 26.06, was released June 21, 2026. The next scheduled end of life is 26.06 on January 31, 2027 — 130 days from this build.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does postmarketOS end of life mean for your organization?
When a version of postmarketOS 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps 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.
Your options when postmarketOS reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Commercial extended support | Not available for postmarketOS from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →