Short answer: Several widely used server platforms reach a support milestone in 2027 — among them Windows Server 2016 (extended support ends January 2027), Ubuntu 22.04 LTS (standard security maintenance ends around May 2027), CentOS Stream 9, Node.js 22, Python 3.11 and PHP 8.3. These are not all the same kind of date — some are firm end-of-support cutoffs, some are projected, and some are minimum support commitments — so treat the table below as a planning starting point and confirm each one on the vendor’s own lifecycle page before you schedule work.
Running end-of-life (EOL) software is a risk, not an automatic failure. Once a release leaves its support stream the upstream project stops shipping fixes for it, so newly found vulnerabilities go unpatched on that stream — though vendor backports or paid extended coverage (Windows ESU, Ubuntu Pro, RHEL) can change that. It also raises compliance risk: PCI-DSS, HIPAA and SOC 2 expect supported software or a documented risk assessment and compensating controls, not an instant pass/fail. The practical takeaway is the same: know the dates, confirm them, and upgrade with a buffer.
2027 support-milestone calendar
Date certainty key: Confirmed = vendor-published cutoff · Scheduled = on the published release cadence · Approximate = month known, exact day not fixed · Projected = expected upstream date that can be extended · Minimum = a “supported at least until” commitment, not an announced end.
| Software & version | Support stream | Milestone (2027) | Certainty | Official source |
|---|---|---|---|---|
| Windows Server 2016 (LTSC) | Extended support (ESU sold after) | January 13, 2027 | Confirmed — some older Microsoft lists show Jan 12 | Microsoft lifecycle |
| CentOS Stream 9 | Full support | May 2027 | Confirmed | Red Hat |
| Ubuntu 22.04 LTS “Jammy” | Standard security maintenance (ESM via Ubuntu Pro to 2032) | ~ May 2027 | Confirmed | Canonical |
| Node.js 22 (LTS) | Maintenance LTS ends | April 30, 2027 | Scheduled | Node.js |
| Python 3.11 | Security-only support | ~ October 2027 | Approximate — no fixed day | python.org |
| Eclipse Temurin (Java 11 & 17) | Adoptium availability | at least October 2027 | Minimum commitment — not an announced EOL | Adoptium |
| PHP 8.3 | Security support | December 31, 2027 | Scheduled | php.net |
| Linux kernel 6.1 & 6.6 LTS | Upstream LTS (distro kernels differ) | December 2027 | Projected — extensions possible | kernel.org |
The dates most servers will actually hit
- Windows Server 2016 — January 2027. Microsoft’s current product-lifecycle page lists January 13, 2027 for end of extended support (older annual summaries say January 12). After it, move to Server 2022/2025 or buy Extended Security Updates.
- Ubuntu 22.04 LTS — around May 2027. Standard security maintenance ends; enable Ubuntu Pro for ESM coverage (free for up to 5 machines) through 2032, or upgrade to 24.04 LTS.
- CentOS Stream 9 — May 2027. Migrate to AlmaLinux or Rocky Linux (9 or 10), or CentOS Stream 10.
- PHP 8.3 — December 31, 2027. Budget a move to 8.4 or 8.5 during 2027. Note: PHP 8.2 is not yet end-of-life — it gets security fixes through December 31, 2026 — while PHP 8.1 reached EOL at the end of 2025.
How to plan the migration
- Inventory first. Audit every server’s OS, PHP, database and runtime versions.
- Sort by confirmed date and exposure — internet-facing and data-handling systems first.
- Confirm each date on the vendor’s lifecycle page; separate firm cutoffs from projected or minimum-commitment dates.
- Test in staging — especially for Tomcat (9.0 → 9.1 is a smaller change than the Jakarta-namespace move to 10/11) and major PHP or database jumps.
- Finish a month early, not on the date.
Frequently asked questions
What happens if I keep running software after its end-of-life date?
It keeps working, but the upstream project stops shipping security fixes for that release, so newly found vulnerabilities go unpatched on that stream. Some vendors sell extended coverage (Windows ESU, Ubuntu Pro, RHEL) or backport fixes, so check whether a paid or extended support stream applies to you.
Does unsupported software automatically fail PCI, HIPAA or SOC 2?
Not automatically. Running unsupported software raises risk, but these frameworks expect a risk assessment rather than an instant verdict: HIPAA requires a documented risk analysis, and PCI DSS allows compensating controls. Document the risk and your mitigations.
Is PHP 8.2 end-of-life?
Not yet. PHP 8.2 receives security fixes through December 31, 2026. PHP 8.1 reached end of life at the end of 2025. Plan your move off 8.2 before the 2026 cutoff, and off 8.3 before its December 31, 2027 date.
Which 2027 end-of-life affects the most servers?
Windows Server 2016 (January 2027) and Ubuntu 22.04 LTS (standard support ending around May 2027) touch the largest install bases, with PHP 8.3 (December 31, 2027) close behind for web hosts.
