postmarketOS · Lifecycle Status

postmarketOS End of Life (EOL) Dates & Support Timeline

Q: What is the latest supported version of postmarketOS?

The latest active version of postmarketOS is 25.12. Always verify against the table above as support windows can change.

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.

Latest Active

25.12

25.12 series

Next EOL

—

None upcoming

Active Versions

of 10 total

EOL Versions

no longer patched

Medium Risk

EOL Risk Score™ How is this calculated? →

EOL Recency

30/40

Attack Surface

10/30 Medium tier

CISA KEV Exposure

0/20 Not in KEV

Extended Support

10/10 None available

EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →

Release Cycle Timeline

■ EOL ■ Warning ■ Active ┊ Today

All Versions

Version	Latest Release	Release Date	EOL Date	Days	Status
21.06	21.06	Jul 4, 2021	Jan 29, 2022	1606 days past EOL	EOL
21.12	21.12	Dec 29, 2021	Jul 12, 2022	1442 days past EOL	EOL
22.06	22.06	Jun 12, 2022	Jan 18, 2023	1252 days past EOL	EOL
22.12	22.12	Dec 18, 2022	Jul 7, 2023	1082 days past EOL	EOL
23.06	23.06	Jun 7, 2023	Jan 18, 2024	887 days past EOL	EOL
23.12	23.12	Dec 18, 2023	Jul 16, 2024	707 days past EOL	EOL
24.06	24.06	Jun 16, 2024	Jan 23, 2025	516 days past EOL	EOL
24.12	24.12	Dec 23, 2024	Jul 23, 2025	335 days past EOL	EOL
25.06	25.06	Jun 23, 2025	Jan 23, 2026	151 days past EOL	EOL
25.12	25.12	Dec 23, 2025	TBD	Supported	Active

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

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →

Frequently Asked Questions

What is the end-of-life date for postmarketOS?

See the full table above for all postmarketOS version EOL dates.

When is the postmarketOS support end date?

Each postmarketOS version has its own support end date — see the table above for every version's date.

What is the latest supported version of postmarketOS?

The latest active version of postmarketOS is 25.12. Always verify against the table above as support windows can change.

What happens when postmarketOS reaches end of life?

When postmarketOS reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.

How do I check if I'm running an EOL version of postmarketOS?

Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.

Is there extended support available for EOL postmarketOS versions?

Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →