[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fW0BEYNZIWVJG3_Tc3yFo8iIpTs_TPSiNYkYjiY5lcHI":3},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover_image_url":9,"author":10,"published_at":11,"created_at":12,"updated_at":12,"is_published":13},"a2422ace-6384-4e2c-bd95-bd5dc9e59ee0","top-10-eol-technologies-q3-2026","Top 10 Technologies Reaching End of Life in Q3 2026","Node.js 18, Ubuntu 20.04, PHP 8.1 and 7 others are losing vendor support this quarter. Here is exactly what expires, when, and what to do about it.","\u003Carticle>\n\u003Cp>Every quarter, a wave of technologies quietly crosses the end-of-life threshold — no fanfare, no automatic upgrade, just a vendor that stops shipping security patches. Q3 2026 is no exception. We pulled the data from EOLCanary's database of 459 tracked technologies to identify every version losing support between July 1 and September 30, 2026.\u003C\u002Fp>\n\u003Cp>Running any of these in production means new CVEs will be discovered and never fixed. Not eventually — never.\u003C\u002Fp>\n\u003Ch2>1. Node.js 18.x — EOL: April 30, 2025\u003C\u002Fh2>\n\u003Cp>Node.js 18 entered LTS in October 2022 and was one of the most widely deployed runtimes of its generation. As of April 2025 it no longer receives security patches. EOLCanary currently tracks 23 CVEs against Node.js 18.x, of which 4 are rated Critical.\u003C\u002Fp>\n\u003Ch2>2. Ubuntu 20.04 LTS — EOL: April 2025\u003C\u002Fh2>\n\u003Cp>Ubuntu 20.04 Focal Fossa was the workhorse of cloud deployments for five years. Standard support ended in April 2025. The kernel, OpenSSL, and Python versions shipped with 20.04 are all receiving zero patches from Canonical.\u003C\u002Fp>\n\u003Ch2>3. PHP 8.1 — EOL: December 31, 2025\u003C\u002Fh2>\n\u003Cp>PHP 8.1 introduced enums, fibers, and intersection types. Its security support ended December 2025. PHP has historically been one of the most CVE-heavy languages in EOLCanary's database.\u003C\u002Fp>\n\u003Ch2>4. Kubernetes 1.29 — EOL: June 2025\u003C\u002Fh2>\n\u003Cp>Kubernetes releases a new minor version every four months and supports each for approximately 14 months. K8s 1.29 hit EOL in June 2025. Clusters still on 1.29 are missing security fixes in the API server, kubelet, and etcd components.\u003C\u002Fp>\n\u003Ch2>5. Redis 6.2 — EOL: March 2024\u003C\u002Fh2>\n\u003Cp>Redis 6.2 reached EOL in March 2024. EOLCanary tracks 18 CVEs against Redis 6.x, making it the most CVE-affected Redis branch in our database. Two of those CVEs appear on the CISA Known Exploited Vulnerabilities list.\u003C\u002Fp>\n\u003Ch2>6. PostgreSQL 13 — EOL: November 2025\u003C\u002Fh2>\n\u003Cp>PostgreSQL 13 reached EOL in November 2025. PostgreSQL CVEs tend to be low in volume but high in severity — running an unsupported major version is a compliance risk for any PCI-DSS or SOC2 environment.\u003C\u002Fp>\n\u003Ch2>7. Django 3.2 LTS — EOL: April 2024\u003C\u002Fh2>\n\u003Cp>Django 3.2 was the last LTS release before 4.x. It reached end of life in April 2024. Django 3.2 applications are now accumulating unpatched vulnerabilities at a faster rate than most other frameworks.\u003C\u002Fp>\n\u003Ch2>8. Amazon EKS 1.28 — EOL: May 2025\u003C\u002Fh2>\n\u003Cp>EKS 1.28 lost support in May 2025. AWS will force-upgrade clusters that remain on unsupported versions, but the transition window is finite.\u003C\u002Fp>\n\u003Ch2>9. Ruby 3.1 — EOL: March 2025\u003C\u002Fh2>\n\u003Cp>Ruby 3.1 reached end of life in March 2025. Teams running Rails applications on Ruby 3.1 should target Ruby 3.3 as the migration path.\u003C\u002Fp>\n\u003Ch2>10. .NET 7 — EOL: May 2024\u003C\u002Fh2>\n\u003Cp>.NET 7 was a Standard Term Support release with an 18-month lifecycle. It expired in May 2024. .NET 7 applications should be targeting .NET 8 LTS.\u003C\u002Fp>\n\u003Ch2>How to track your stack automatically\u003C\u002Fh2>\n\u003Cp>EOLCanary monitors 459 technologies and alerts you by email before a version in your declared stack reaches end of life. The alert system covers EOL thresholds at 6 months, 3 months, 1 month, and 1 week — giving your team enough runway to plan upgrades without emergency patches.\u003C\u002Fp>\n\u003C\u002Farticle>","\u002Fblog\u002Ftop-10-eol-q3-2026.png","EOLCanary Team","2026-06-16T08:00:00+00:00","2026-06-26T13:44:04.556818+00:00",true]