End-of-life software still running
Software past its end-of-life date stops receiving security fixes, so new vulnerabilities in it stay open forever. It's a slow but certain risk.
Why it matters
A new critical bug in an EOL runtime (an old PHP, Node, Python, or an unsupported OS) will never be patched — your only fix is to upgrade, under pressure, during an incident.
Compliance frameworks and cyber-insurance increasingly treat EOL software as an automatic finding.
How to check for it
- Compare your OS, kernel, language runtimes and databases against endoflife.date.
- Common offenders: CentOS 7, Ubuntu past its LTS window, PHP 7.x, Node 16 and earlier, Python 3.7 and earlier.
How to fix it
- Plan upgrades before the EOL date, not after; track them as you would any dependency.
- Where an immediate upgrade isn't possible, isolate the host and limit its exposure until it's done.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.